CVE-2022-20498: libfdt_fuzzer Stack-overflow in fdt_path_offset_namelen
Summary
CVE-2022-20498: In fdt_path_offset_namelen of fdt_ro.c, there is a possible out of bounds read due to an incorrect bounds check. Affects platform/external/dtc across 5 version ranges.
>= 10:0, < 10:2022-12-01
>= 11:0, < 11:2022-12-01
>= 12:0, < 12:2022-12-01
>= 12L:0, < 12L:2022-12-01
>= 13:0, < 13:2022-12-01
Fixed in 10:2022-12-01. How to fix ↓
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.
No signup required · Results in about 60 seconds
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The package under scrutiny is platform/external/dtc, which is part of the Android ecosystem. Dtc is a device tree compiler and decompiler tool used for manipulating device tree files. Device tree files are used in the boot process of many embedded systems to describe the hardware configuration. The vulnerability affects versions 10, 11, 12, 12L, and 13 of the package.
Vulnerability Detail
The vulnerability, identified as CVE-2022-20498, resides in the fdt_path_offset_namelen function of fdt_ro.c. It is caused by an incorrect bounds check, leading to a possible out-of-bounds read. Exploiting this vulnerability could result in local information disclosure, requiring system execution privileges. It is important to note that user interaction is not necessary for exploitation.
How To Fix
Minimum fixed version
10:2022-12-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 libfdt_fuzzer vulnerability in fdt_path_offset_namelen poses a risk of local information disclosure. It is crucial to update the dtc package to the fixed version to mitigate this vulnerability. For further support on vulnerability remediation, you can reach out to DevNack.com.
See every vulnerability recorded for platform/external/dtc →
FAQ
This vulnerability could lead to local information disclosure, potentially exposing sensitive data.
Exploiting this vulnerability requires system execution privileges.
No, user interaction is not needed for exploitation.
Versions 10, 11, 12, 12L, and 13 of the platform/external/dtc package are affected.
For more information about this vulnerability, you can refer to the source: https://storage.googleapis.com/android-osv/ASB-A-246465319.json
Related vulnerabilities
Recent vulnerabilities recorded for platform/external/dtc.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
