Google Android fdt_ro.c fdt_path_offset_namelen 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.
3.3$0-$5k0.00

Summaryinfo

A vulnerability was found in Google Android. It has been classified as problematic. The impacted element is the function fdt_path_offset_namelen of the file fdt_ro.c. This manipulation causes out-of-bounds. This vulnerability is registered as CVE-2022-42543. The attack needs to be launched locally. No exploit is available. It is suggested to install a patch to address this issue.

Detailsinfo

A vulnerability was found in Google Android (Smartphone Operating System) (unknown version). It has been declared as problematic. Affected by this vulnerability is the function fdt_path_offset_namelen of the file fdt_ro.c. The manipulation with an unknown input leads to a out-of-bounds vulnerability. The CWE definition for the vulnerability is CWE-125. The product reads data past the end, or before the beginning, of the intended buffer. As an impact it is known to affect confidentiality. The summary by CVE is:

In fdt_path_offset_namelen of fdt_ro.c, there is a possible out of bounds read due to an incorrect 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-249998113References: N/A

The weakness was published 12/16/2022 as A-249998113. The advisory is shared at source.android.com. This vulnerability is known as CVE-2022-42543 since 10/07/2022. Technical details are known, but no exploit is available.

Applying a patch is able to eliminate this problem.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

Vendor

Name

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

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

CVSSv2info

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

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

Exploitinginfo

Class: Out-of-bounds
CWE: CWE-125 / 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

10/07/2022 🔍
12/16/2022 +70 days 🔍
12/16/2022 +0 days 🔍
04/17/2025 +853 days 🔍

Sourcesinfo

Vendor: google.com

Advisory: A-249998113
Status: Confirmed

CVE: CVE-2022-42543 (🔍)
GCVE (CVE): GCVE-0-2022-42543
GCVE (VulDB): GCVE-100-216025
scip Labs: https://www.scip.ch/en/?labs.20150917

Entryinfo

Created: 12/16/2022 20:55
Updated: 04/17/2025 23:24
Changes: 12/16/2022 20:55 (42), 01/13/2023 18:45 (11), 04/17/2025 23:24 (16)
Complete: 🔍
Cache ID: 216::103

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Want to know what is going to be exploited?

We predict KEV entries!