CVE-2022-20453: Path traversal leading to permanent DoS in TelephonyProvider

Summary

01/11/2022
Yes i
High
Not published

CVE-2022-20453: In update of MmsProvider.java, there is a possible constriction of directory permissions due to a path traversal error. Affects platform/packages/providers/TelephonyProvider across 5 version ranges.

>= 10:0, < 10:2022-11-01 >= 11:0, < 11:2022-11-01 >= 12:0, < 12:2022-11-01 >= 12L:0, < 12L:2022-11-01 >= 13:0, < 13:2022-11-01

Fixed in 10:2022-11-01. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

TelephonyProvider is a package in the Android ecosystem that provides telephony-related functionality to Android devices. It is responsible for managing MMS (Multimedia Messaging Service) data and interactions. MmsProvider.java is a component of TelephonyProvider that handles the update process. This vulnerability affects versions 10 and above of the Android platform. The vulnerability allows for a path traversal error, resulting in a constriction of directory permissions. This can lead to a local denial of service (DoS) attack on SIM recognition. Exploitation of this vulnerability requires user interaction.

Vulnerability Detail

The vulnerability in MmsProvider.java arises from a path traversal error in the update process. Due to this error, there is a constriction of directory permissions, which can be exploited to cause a local denial of service attack on SIM recognition. The attacker does not require additional execution privileges to exploit this vulnerability. The impact of this vulnerability is a permanent DoS on SIM recognition. It is important to note that user interaction is necessary for successful exploitation of this vulnerability.

How To Fix

Minimum fixed version

10:2022-11-01

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

There is no specific workaround mentioned for this vulnerability.

Conclusion

In conclusion, the TelephonyProvider package in the Android ecosystem is vulnerable to a path traversal issue in the MmsProvider.java component. This vulnerability can be exploited to cause a local denial of service attack on SIM recognition. It is recommended to apply the provided fix from the Android Open Source Project to mitigate this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for platform/packages/providers/TelephonyProvider →

Share this vulnerability

FAQ

TelephonyProvider is a package in the Android ecosystem that provides telephony-related functionality to Android devices. It is responsible for managing MMS data and interactions.

MmsProvider.java is a component of TelephonyProvider that handles the update process for MMS data.

A path traversal vulnerability occurs when an attacker can navigate outside of the intended directory structure and access files or directories that should be restricted.

SIM recognition refers to the process of identifying and authenticating the SIM card inserted in a mobile device.

Yes, user interaction is necessary for successful exploitation of this vulnerability.

Related vulnerabilities

Recent vulnerabilities recorded for platform/packages/providers/TelephonyProvider.

How To Fix

Minimum fixed version

10:2022-11-01

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

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 →
Help improve this record
Report an issue or send feedback