CVE-2022-23815: Improper bounds checking in APCB firmware may allow an attacker to perform an out of bounds write, corrupting the APCB entry, potentially…
Noroxi assessment
Priority: Monitor (action score 32/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.16% (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.
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
Improper bounds checking in APCB firmware may allow an attacker to perform an out of bounds write, corrupting the APCB entry, potentially leading to arbitrary code execution.
- Published
- Aug 13, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.1% · 5th percentile
- CWE
- CWE-787
Report tools
Action score
32
Low priority for now.
- CVSS
- 32 / 40 · 8.2 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 8.2
- CNA · AMD
- 7.5
- 0.7 point gap
CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
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.
Is your version affected? Check itNoroxi 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 |
|---|---|---|
| amd | athlon silver 3050u firmware | cpe:2.3:o:amd:athlon_silver_3050u_firmware |
| amd | athlon silver 3050u | cpe:2.3:h:amd:athlon_silver_3050u |
| amd | athlon gold 3150u firmware | cpe:2.3:o:amd:athlon_gold_3150u_firmware |
| amd | athlon gold 3150u | cpe:2.3:h:amd:athlon_gold_3150u |
| amd | ryzen 7 3780u firmware | cpe:2.3:o:amd:ryzen_7_3780u_firmware |
| amd | ryzen 7 3780u | cpe:2.3:h:amd:ryzen_7_3780u |
| amd | ryzen 7 3750h firmware | cpe:2.3:o:amd:ryzen_7_3750h_firmware |
| amd | ryzen 7 3750h | cpe:2.3:h:amd:ryzen_7_3750h |
| amd | ryzen 7 pro 3700u firmware | cpe:2.3:o:amd:ryzen_7_pro_3700u_firmware |
| amd | ryzen 7 pro 3700u | cpe:2.3:h:amd:ryzen_7_pro_3700u |
| amd | ryzen 7 3700u firmware | cpe:2.3:o:amd:ryzen_7_3700u_firmware |
| amd | ryzen 7 3700u | cpe:2.3:h:amd:ryzen_7_3700u |
and 20 more
Versions reported by the vendor
Affected version ranges reported by the assigning authority (AMD). Independent of NVD's CPE analysis and usually ahead of it.
AMD AMD Athlon™ 3000 Series Desktop Processors with Radeon™ Graphics
- variousaffected
AMD AMD Athlon™ 3000 Series Mobile Processors with Radeon™ Graphics
- PicassoPI-FP5 1.0.0.F, PollockPI-FT5 1.0.0.5not affected
AMD AMD Ryzen™ 3000 Series Mobile Processor with Radeon™ Graphics
- PicassoPI-FP5 1.0.0.Enot affected
AMD AMD RyzenTM Embedded R1000
- EmbeddedPI-FP5 1.2.0.Anot affected
AMD AMD RyzenTM Embedded R2000
- EmbeddedR2KPI-FP5 1.0.0.2not affected
AMD AMD RyzenTM Embedded V1000
- EmbeddedPI-FP5 1.2.0.Anot affected
Affected versions · NVD (16)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- amd athlon gold 3150g firmwareall versions
- amd athlon gold 3150u firmwarebefore picassopi-fp5_1.0.0.e
- amd athlon gold pro 3150g firmwareall versions
- amd athlon gold pro 3150ge firmwareall versions
- amd athlon pro 300ge firmwareall versions
- amd athlon silver 3050u firmwarebefore picassopi-fp5_1.0.0.e
- amd ryzen 3 3200u firmwarebefore picassopi-fp5_1.0.0.e
- amd ryzen 3 3250u firmwarebefore picassopi-fp5_1.0.0.e
- amd ryzen 3 3300u firmwarebefore picassopi-fp5_1.0.0.e
- amd ryzen 5 3500u firmwarebefore picassopi-fp5_1.0.0.e
- amd ryzen 5 3550h firmwarebefore picassopi-fp5_1.0.0.e
- amd ryzen 5 3580u firmwarebefore picassopi-fp5_1.0.0.e
- amd ryzen 7 3700u firmwarebefore picassopi-fp5_1.0.0.e
- amd ryzen 7 3750h firmwarebefore picassopi-fp5_1.0.0.e
- amd ryzen 7 3780u firmwarebefore picassopi-fp5_1.0.0.e
- amd ryzen 7 pro 3700u firmwarebefore picassopi-fp5_1.0.0.e
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.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
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
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
Impact can extend beyond the vulnerable component (scope changes).
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- High
- User interaction
- None
- Scope
- Changed
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-787 · Out-of-bounds WriteCVSS vector
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
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.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (0)
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.