Google Android protocolimsbuilder.cpp BuildSetConfig out-of-bounds
|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.
A vulnerability was found in Google Android (Smartphone Operating System) (the affected version unknown). It has been classified as problematic. This affects the function
ProtocolImsBuilder::BuildSetConfig of the file protocolimsbuilder.cpp. The manipulation with an unknown input leads to a out-of-bounds vulnerability. CWE is classifying the issue as CWE-125. The software reads data past the end, or before the beginning, of the intended buffer. This is going to have an impact on confidentiality. The summary by CVE is:
In ProtocolImsBuilder::BuildSetConfig of protocolimsbuilder.cpp, there is a possible out of bounds read due to a missing bounds check. This could lead to local information disclosure with System execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android kernelAndroid ID: A-241763298References: N/A
The weakness was published 12/16/2022 as A-241763298. It is possible to read the advisory at source.android.com. This vulnerability is uniquely identified as CVE-2022-42514 since 10/07/2022. Technical details of the vulnerability are known, but there is no available exploit. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 01/13/2023). 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.
CVSSv3VulDB Meta Base Score: 3.3
VulDB Meta Temp Score: 3.3
VulDB Base Score: 2.3
VulDB Temp Score: 2.2
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 4.4
NVD Vector: 🔒
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
CWE: CWE-125 / CWE-119
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
Threat IntelligenceInterest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍
0-Day Time: 🔒
Timeline10/07/2022 CVE reserved
12/16/2022 +70 days Advisory disclosed
12/16/2022 +0 days VulDB entry created
01/13/2023 +28 days VulDB last update
CVE: CVE-2022-42514 (🔒)
scip Labs: https://www.scip.ch/en/?labs.20150917
EntryCreated: 12/16/2022 07:59 PM
Updated: 01/13/2023 05:45 PM
Changes: 12/16/2022 07:59 PM (42), 01/13/2023 05:45 PM (11)
Do you want to use VulDB in your project?
Use the official API to access entries easily!
No comments yet. Languages: en.
Please log in to comment.