CVE-2024-20145
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIn V6 DA, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of privilege, if an attacker has physical access to the device, with no additional execution privileges needed. User interaction is needed for exploitation. Patch ID: ALPS09290940; Issue ID: MSV-2040.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA missing bounds check in V6 DA allows an out-of-bounds write vulnerability, which can be exploited for local privilege escalation. The attacker requires physical access to the device and user interaction to trigger the flaw.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 4.0= 2022q3= 2024q1= 14.0= 15.0= 19.07.0= 21.02.0= 23.05CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Physical
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:P/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the operating system and versionRun commands such as 'cat /etc/os-release' on Linux-based systems, or check the device firmware/system information to determine if the system is running Yocto 4.0, RDK B 2022q3, RDK B 2024q1, Android 14.0/15.0, OpenWRT 19.07.0, 21.02.0, or 23.05Affected if The system matches one of these specific versions listed in the affected products
-
Locate the V6 DA componentSearch for V6 DA related binaries, drivers, or modules on the system using 'find / -name "*v6*" -o -name "*v6da*"' or check for device driver files typically found in /dev, /lib/modules, or vendor-specific directoriesAffected if The V6 DA component is present on the system
-
Check if the vulnerable code path is accessibleVerify that the V6 DA functionality is exposed and can be invoked through available interfaces, device nodes, or system callsAffected if The V6 DA component is loaded and accessible to local users with physical access
-
Verify physical access conditionsConfirm whether the device or system is physically accessible to untrusted individuals, as the vulnerability requires physical access and user interaction to triggerAffected if Physical access to the device is not restricted or controlled
A system is affected if it runs one of the listed versions (Yocto 4.0, RDK B 2022q3/2024q1, Android 14.0/15.0, OpenWRT 19.07.0/21.02.0/23.05) AND has the V6 DA component present and accessible, AND physical access with user interaction is feasible for an attacker.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply vendor patch ALPS09290940. Until patched, restrict physical access to vulnerable devices and monitor for suspicious user activity.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-20145 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-20145 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data