CVE-2024-20085

In power, 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. Patch ID: ALPS08944204; Issue ID: MSV-1560.

Published: 2024-09-02 Last update: 2024-10-27 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2024-20085 is rated Low Risk (20.9/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.04%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2024-20085

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2024-09-02 — 0.04% —

Full EPSS history (1 record total)

Common vulnerability scoring system (CVSS) metrics for CVE-2024-20085

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
4.4 3.1 MEDIUM
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:H)
They need powerful rights—admin, root, or similar—before this pays off.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
 0.8 3.6 [email protected]
4.4 3.1 MEDIUM
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:H)
They need powerful rights—admin, root, or similar—before this pays off.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
 0.8 3.6 134c704f-9b21-4f2e-91b3-4a467353bcc0

Weakness enumeration for CVE-2024-20085

Affected software / configurations for CVE-2024-20085

Vendor Product Version Raw CPE
linuxfoundation yocto 2.6 cpe:2.3:a:linuxfoundation:yocto:2.6:*:*:*:*:*:*:*
linuxfoundation yocto 3.3 cpe:2.3:a:linuxfoundation:yocto:3.3:*:*:*:*:*:*:*
linuxfoundation yocto 4.0 cpe:2.3:a:linuxfoundation:yocto:4.0:*:*:*:*:*:*:*
rdkcentral rdk-b 2022q3 cpe:2.3:a:rdkcentral:rdk-b:2022q3:*:*:*:*:*:*:*
google android 13.0 cpe:2.3:o:google:android:13.0:*:*:*:*:*:*:*
google android 14.0 cpe:2.3:o:google:android:14.0:*:*:*:*:*:*:*
openwrt openwrt 19.07.0 cpe:2.3:o:openwrt:openwrt:19.07.0:*:*:*:*:*:*:*
openwrt openwrt 21.02 cpe:2.3:o:openwrt:openwrt:21.02:*:*:*:*:*:*:*
openwrt openwrt 22.03.5 cpe:2.3:o:openwrt:openwrt:22.03.5:*:*:*:*:*:*:*

References for CVE-2024-20085

cvelogic Threat Intelligence