Google Android 9.0/10.0/11.0/12.0 LegacyModeSmsHandler.java sendLegacyVoicemailNotification permission

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
5.1$5k-$25k0.00

A vulnerability was found in Google Android 9.0/10.0/11.0/12.0 (Smartphone Operating System). It has been classified as critical. This affects the function sendLegacyVoicemailNotification of the file LegacyModeSmsHandler.java. The manipulation with an unknown input leads to a privilege escalation vulnerability. CWE is classifying the issue as CWE-275. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

In sendLegacyVoicemailNotification of LegacyModeSmsHandler.java, there is a possible permissions bypass due to an unsafe PendingIntent. This could lead to local escalation of privilege with User execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-10 Android-11 Android-12 Android-9Android ID: A-185126549

The weakness was presented 01/15/2022 as A-185126549. It is possible to read the advisory at source.android.com. This vulnerability is uniquely identified as CVE-2021-39627 since 08/23/2021. The exploitability is told to be easy. Attacking locally is a requirement. A authentication is required for exploitation. Technical details of the vulnerability are known, but there is no available exploit. The pricing for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 01/19/2022). It is expected to see the exploit prices for this product increasing in the near future.The attack technique deployed by this issue is T1222 according to MITRE ATT&CK.

Applying a patch is able to eliminate this problem.

Productinfoedit

Type

Vendor

Name

CPE 2.3infoedit

CPE 2.2infoedit

CVSSv3infoedit

VulDB Meta Base Score: 5.3
VulDB Meta Temp Score: 5.1

VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2infoedit

AVACAuCIA
🔍🔍🔍🔍🔍🔍
🔍🔍🔍🔍🔍🔍
🔍🔍🔍🔍🔍🔍
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
unlockunlockunlockunlockunlockunlock
unlockunlockunlockunlockunlockunlock
unlockunlockunlockunlockunlockunlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfoedit

Class: Privilege escalation
CWE: CWE-275
ATT&CK: T1222

Local: Yes
Remote: No

Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒

0-Dayunlockunlockunlockunlock
Todayunlockunlockunlockunlock

Threat Intelligenceinfoedit

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfoedit

Recommended: Patch
Status: 🔍

0-Day Time: 🔒

Patch: source.android.com

Timelineinfoedit

08/23/2021 CVE assigned
01/15/2022 +145 days Advisory disclosed
01/15/2022 +0 days VulDB entry created
01/19/2022 +4 days VulDB last update

Sourcesinfoedit

Vendor: https://www.google.com/

Advisory: A-185126549
Status: Confirmed

CVE: CVE-2021-39627 (🔒)
scip Labs: https://www.scip.ch/en/?labs.20150917

Entryinfoedit

Created: 01/15/2022 08:09 AM
Updated: 01/19/2022 02:24 PM
Changes: (1) source_cve_nvd_summary
Complete: 🔍

Comments

No comments yet. Languages: en.

Please log in to comment.

Do you want to use VulDB in your project?

Use the official API to access entries easily!