CVE-2023-20915: Bypassing User Interaction in Phone Account Settings

Summary

01/01/2023
Yes i
High
Not published

CVE-2023-20915: In addOrReplacePhoneAccount of PhoneAccountRegistrar.java, there is a possible way to enable a phone account without user interaction due to a logic error in the code. Affects platform/packages/services/Telecomm across 5 version ranges.

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

Fixed in 10:2023-01-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 Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The package under scrutiny is platform/packages/services/Telecomm, which is a part of the Android ecosystem. This package is responsible for managing phone account settings on Android devices. It enables users to configure and manage their phone accounts, including SIM cards, phone numbers, and associated services. The package plays a crucial role in ensuring proper communication functionality on Android devices.

Vulnerability Detail

The vulnerability, identified as CVE-2023-20915, resides in the addOrReplacePhoneAccount function of PhoneAccountRegistrar.java. Due to a logic error in the code, it is possible to enable a phone account without requiring any user interaction. This flaw can be exploited to escalate local privileges without the need for additional execution privileges. The vulnerability does not rely on user interaction, making it particularly dangerous. If exploited, an attacker could gain unauthorized access to phone account settings and potentially manipulate or abuse phone services.

How To Fix

Minimum fixed version

10:2023-01-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

No workaround has been provided for this vulnerability.

Conclusion

In conclusion, the vulnerability CVE-2023-20915 allows for the bypassing of user interaction in phone account settings, potentially leading to local privilege escalation. It is crucial to apply the provided fix to ensure the proper functioning and security of phone account management on Android devices. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for platform/packages/services/Telecomm →

Share this vulnerability

FAQ

If exploited, this vulnerability allows an attacker to bypass user interaction and enable a phone account without authorization. This can lead to local privilege escalation, potentially compromising the security and integrity of phone account settings.

No, user interaction is not needed for exploitation of this vulnerability.

The vulnerability was introduced in Android 10 and affects all subsequent versions up to Android 13.

There are no known instances of this vulnerability being exploited in the wild at the time of this report.

You can use the Vulert Playground at Vulert Scanner to check if your application is affected by this vulnerability. Vulert monitors and alerts in real-time for open-source vulnerabilities, using only the gradle.lockfile, without requiring access to the code or installation.

Related vulnerabilities

Recent vulnerabilities recorded for platform/packages/services/Telecomm.

How To Fix

Minimum fixed version

10:2023-01-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