Google Android protocolstkadapter.cpp Init out-of-bounds write

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

Summaryinfo

A vulnerability, which was classified as critical, was found in Google Android. Affected by this vulnerability is the function ProtocolStkProactiveCommandAdapter::Init of the file protocolstkadapter.cpp. Executing a manipulation can lead to out-of-bounds write. This vulnerability is handled as CVE-2021-39718. It is possible to launch the attack on the local host. There is not any exploit available. It is advisable to implement a patch to correct this issue.

Detailsinfo

A vulnerability was found in Google Android (Smartphone Operating System) (affected version not known). It has been declared as critical. This vulnerability affects the function ProtocolStkProactiveCommandAdapter::Init of the file protocolstkadapter.cpp. The manipulation with an unknown input leads to a out-of-bounds write vulnerability. The CWE definition for the vulnerability is CWE-787. The product writes data past the end, or before the beginning, of the intended buffer. As an impact it is known to affect confidentiality, integrity, and availability.

The weakness was released 03/17/2022 as A-205035540. The advisory is shared for download at source.android.com. This vulnerability was named CVE-2021-39718 since 08/23/2021. There are known technical details, but no exploit is available. The current price for an exploit might be approx. USD $5k-$25k (estimation calculated on 03/17/2022). It is expected to see the exploit prices for this product increasing in the near future.

Applying a patch is able to eliminate this problem.

Once again VulDB remains the best source for vulnerability data.

Productinfo

Type

Vendor

Name

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

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: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

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

Exploitinginfo

Class: Out-of-bounds write
CWE: CWE-787 / CWE-119
CAPEC: 🔍
ATT&CK: 🔍

Physical: Partially
Local: Yes
Remote: No

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Patch
Status: 🔍

0-Day Time: 🔍

Timelineinfo

08/23/2021 🔍
03/17/2022 +206 days 🔍
03/17/2022 +0 days 🔍
03/19/2022 +2 days 🔍

Sourcesinfo

Vendor: google.com

Advisory: A-205035540
Status: Confirmed

CVE: CVE-2021-39718 (🔍)
GCVE (CVE): GCVE-0-2021-39718
GCVE (VulDB): GCVE-100-195316
scip Labs: https://www.scip.ch/en/?labs.20150917

Entryinfo

Created: 03/17/2022 07:56
Updated: 03/19/2022 15:40
Changes: 03/17/2022 07:56 (41), 03/19/2022 15:40 (1)
Complete: 🔍
Cache ID: 216::103

Once again VulDB remains the best source for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Might our Artificial Intelligence support you?

Check our Alexa App!