VulertSecurity VulertSecurity

Vulnerability Database · Android · Package report

platform/packages/providers/TelephonyProvider: vulnerability history, versions and safety

platform/packages/providers/TelephonyProvider is a package in the Android ecosystem. Vulert records 10 vulnerabilities for it across 6 releases, from Nov 2022 to Sep 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
10 vulnerabilities recorded C1 H6 M3
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
3 in the last 12 months

Most recent disclosure 01 Sep 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all platform/packages/providers/TelephonyProvider vulnerabilities

Vulert verdict on platform/packages/providers/TelephonyProvider i

Updated on 23 Oct 2026

Every vulnerability Vulert records for this package has a fix, and the newest was recorded 01 Sep 2026. Apply the fixes listed below and you are clear.

Long-term outlook: usable, with an upgrade 10 vulnerabilities on record across 3 years, 3 in the last year.

What to do: Move the affected dependencies to the fixed versions listed below, then keep the package monitored so the next vulnerability reaches you. Fix it, then keep watch: Vulert alerts you when a new vulnerability affects the version you run. Monitor it with Vulert →

  • Vulnerabilities on record 10 over 3 years · 3 in the last year i
  • Latest disclosure 01 Sep 2026 i
  • Highest CVSS n/a i
  • With no published fix 0 i

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert holds for platform/packages/providers/TelephonyProvider, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

i
Version Vulert vulnerabilities Fix published Details
17-next H1 Yes Details →
16-qpr2-next H2 Yes Details →
13 M3 Yes Details →
13-next H2 Yes Details →
11 C1 Yes Details →
10 H1 Yes Details →

Newest 6 of 6 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 4
  • 2023 3
  • 2026 3

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 3 of the 10 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for platform/packages/providers/TelephonyProvider

The 5 most severe of 10 vulnerabilities recorded for this package

Search all 10 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2022-20453: Path traversal leading to permanent DoS in TelephonyProvider N/A high 10:2022-11-01 01 Nov 2022
CVE-2023-21290: EoP: chmod arbitrary file permission by race condition in MmsProvider.java N/A high 13-next:2023-08-01 01 Aug 2023
CVE-2023-21268: Directory Permissions Constriction in TelephonyProvider N/A high 13-next:2023-08-01 01 Aug 2023
CVE-2023-40113: Work Profile Messages app having access to personal messages (1) N/A critical 11:2023-11-01 01 Nov 2023
CVE-2022-20517: SQL Injection in MmsSmsProvider#query via URI PathSegments N/A medium 13:2022-12-01 01 Dec 2022

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About platform/packages/providers/TelephonyProvider

Is platform/packages/providers/TelephonyProvider safe to use?

Vulert records 10 vulnerabilities for platform/packages/providers/TelephonyProvider in Android: 1 critical, 6 high, 3 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

How many vulnerabilities does platform/packages/providers/TelephonyProvider have?

10 vulnerabilities are recorded for platform/packages/providers/TelephonyProvider in the Android ecosystem: 1 critical, 6 high, 3 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new platform/packages/providers/TelephonyProvider vulnerabilities disclosed?

3 vulnerabilities were recorded for platform/packages/providers/TelephonyProvider in the last 12 months, and the oldest entry in this database dates to 01 Nov 2022. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of platform/packages/providers/TelephonyProvider are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor platform/packages/providers/TelephonyProvider for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the platform/packages/providers/TelephonyProvider version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.