CVE-2024-20085: In power, there is a possible out of bounds read due to a missing bounds check.
Noroxi assessment
Priority: Monitor (action score 17/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.09% (FIRST EPSS).
- Someone with local access to the system can trigger it. Administrator privileges are required. No user action is required. No special conditions are required; it is repeatable.
- According to the record, no fixed version is available yet.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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
- Sep 2, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.0% · 0th percentile
- CWE
- CWE-125
Report tools
Action score
17
Monitor
Low priority for now.
- CVSS
- 17 / 40 · 4.4 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.0%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linuxfoundation | yocto | cpe:2.3:a:linuxfoundation:yocto |
| rdkcentral | rdk-b | cpe:2.3:a:rdkcentral:rdk-b |
| android | cpe:2.3:o:google:android | |
| openwrt | openwrt | cpe:2.3:o:openwrt:openwrt |
| mediatek | mt6580 | cpe:2.3:h:mediatek:mt6580 |
| mediatek | mt6739 | cpe:2.3:h:mediatek:mt6739 |
| mediatek | mt6761 | cpe:2.3:h:mediatek:mt6761 |
| mediatek | mt6765 | cpe:2.3:h:mediatek:mt6765 |
| mediatek | mt6768 | cpe:2.3:h:mediatek:mt6768 |
| mediatek | mt6779 | cpe:2.3:h:mediatek:mt6779 |
| mediatek | mt6781 | cpe:2.3:h:mediatek:mt6781 |
| mediatek | mt6785 | cpe:2.3:h:mediatek:mt6785 |
and 31 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- google android13.0
- google android14.0
- linuxfoundation yocto2.6
- linuxfoundation yocto3.3
- linuxfoundation yocto4.0
- openwrt openwrt19.07.0
- openwrt openwrt21.02
- openwrt openwrt22.03.5
- rdkcentral rdk-b2022q3
Versions reported by the vendor
Affected version ranges reported by the assigning authority (MediaTek). Independent of NVD's CPE analysis and usually ahead of it.
MediaTek, Inc. MT6580, MT6739, MT6761, MT6765, MT6768, MT6779, MT6781, MT6785, MT6789, MT6833, MT6835, MT6853, MT6855, MT6873, MT6877, MT6879, MT6880, MT6883, MT6885, MT6886, MT6889, MT6890, MT6893, MT6895, MT6897,
- Android 13.0, 14.0 / Yocto 2.6, 3.3, 4.0 / openWRT 19.07, 21.02, 23.05 / RDK-B 22Q3affected
Same product
linuxfoundation: all recordsOther highest-scoring records for the same primary product.
- CVE-2024-20148In wlan STA FW, there is a possible out of bounds write due to improper input validation.39Monitor
- CVE-2024-20080In gnss service, there is a possible escalation of privilege due to improper certificate validation.39Monitor
- CVE-2024-25626Yocto Project Security Advisory - BitBake/Toaster39Monitor
Published before and after this one in the same product
- ← EarlierCVE-2024-20081Jul 1, 2024 · In gnss service, there is a possible out of bounds write due to improper input validation.26Monitor
- ← EarlierCVE-2024-20084Sep 2, 2024 · In power, there is a possible out of bounds read due to a missing bounds check.17Monitor
- Later →CVE-2024-20089Sep 2, 2024 · In wlan, there is a possible denial of service due to incorrect error handling.30Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2024-20022183 days apartIn lk, there is a possible escalation of privilege due to a missing bounds check.26Monitor
- CVE-2025-20693308 days apartIn wlan STA driver, there is a possible out of bounds read due to an incorrect bounds check.26Monitor
- CVE-2023-20840365 days apartIn imgsys, there is a possible out of bounds read and write due to a missing valid range checking.26Monitor
- CVE-2023-20848365 days apartIn imgsys_cmdq, there is a possible out of bounds read due to a missing valid range checking.26Monitor
- CVE-2024-20055155 days apartIn imgsys, there is a possible information disclosure due to a missing bounds check.25Monitor
- CVE-2024-2010762 days apartIn da, there is a possible out of bounds read due to a missing bounds check.24Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-24-1381 · Sep 3, 2024(MediaTek Çoklu Ürün Güvenlik Bildirimi)
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- Administrator privileges are required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-125 · Out-of-bounds ReadCVSS vector
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.