AMD Athlon™ 3000 Series Desktop Processors…: Out-of-bounds Write
CVE-2022-23815 is a high-severity out-of-bounds write vulnerability in AMD Athlon™ 3000 Series Desktop Processors with Radeon™ Graphics from AMD, with a CVSS 3.1 base score of 8.2 out of 10. It can be exploited with local access to the system by an attacker with administrator privileges, without any action from a user. Affected AMD Athlon™ 3000 Series Desktop Processors with Radeon™ Graphics versions: various. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.16% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Athlon Silver 3050u Firmware to picassopi-fp5_1.0.0.e or a later version.
- Update Athlon Gold 3150u Firmware to picassopi-fp5_1.0.0.e or a later version.
- Update Ryzen 7 3780u Firmware to picassopi-fp5_1.0.0.e or a later version.
- Read the advisory on amd.com for workarounds and exact fixed builds.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| AMD | AMD Athlon™ 3000 Series Desktop Processors with Radeon™ Graphics | various | Not stated |
| AMD | AMD Athlon™ 3000 Series Mobile Processors with Radeon™ Graphics | Not specified in the record | Not stated |
| AMD | AMD Ryzen™ 3000 Series Mobile Processor with Radeon™ Graphics | Not specified in the record | Not stated |
| AMD | AMD RyzenTM Embedded R1000 | Not specified in the record | Not stated |
| AMD | AMD RyzenTM Embedded R2000 | Not specified in the record | Not stated |
| AMD | AMD RyzenTM Embedded V1000 | Not specified in the record | Not stated |
| AMD | athlon_3000g | various | Not stated |
| AMD | ryzen_embedded_r1000 | Not specified in the record | Not stated |
| AMD | ryzen_embedded_r2000 | Not specified in the record | Not stated |
| AMD | ryzen_embedded_v1000 | Not specified in the record | Not stated |
| AMD | Athlon Silver 3050u Firmware | before picassopi-fp5_1.0.0.e | picassopi-fp5_1.0.0.e |
| AMD | Athlon Gold 3150u Firmware | before picassopi-fp5_1.0.0.e | picassopi-fp5_1.0.0.e |
| AMD | Ryzen 7 3780u Firmware | before picassopi-fp5_1.0.0.e | picassopi-fp5_1.0.0.e |
| AMD | Ryzen 7 3750h Firmware | before picassopi-fp5_1.0.0.e | picassopi-fp5_1.0.0.e |
| AMD | Ryzen 7 Pro 3700u Firmware | before picassopi-fp5_1.0.0.e | picassopi-fp5_1.0.0.e |
| AMD | Ryzen 7 3700u Firmware | before picassopi-fp5_1.0.0.e | picassopi-fp5_1.0.0.e |
| AMD | Ryzen 5 3580u Firmware | before picassopi-fp5_1.0.0.e | picassopi-fp5_1.0.0.e |
| AMD | Ryzen 5 3550h Firmware | before picassopi-fp5_1.0.0.e | picassopi-fp5_1.0.0.e |
| AMD | Ryzen 5 3500u Firmware | before picassopi-fp5_1.0.0.e | picassopi-fp5_1.0.0.e |
| AMD | Ryzen 3 3300u Firmware | before picassopi-fp5_1.0.0.e | picassopi-fp5_1.0.0.e |
| AMD | Ryzen 3 3250u Firmware | before picassopi-fp5_1.0.0.e | picassopi-fp5_1.0.0.e |
| AMD | Ryzen 3 3200u Firmware | before picassopi-fp5_1.0.0.e | picassopi-fp5_1.0.0.e |
| AMD | Athlon Gold Pro 3150g Firmware | Not specified in the record | Not stated |
| AMD | Athlon Gold 3150g Firmware | Not specified in the record | Not stated |
| AMD | Athlon Gold Pro 3150ge Firmware | Not specified in the record | Not stated |
Version data comes from the organisation that assigned the CVE; 1 further products are omitted here. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- LocalThe attacker needs local access or must trick a user into running something.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- HighAdministrator-level access is required first.
- User interaction
- NoneNo action by a victim is required.
- Scope
- ChangedThe attack can reach beyond the vulnerable component into other systems.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 7.5 | High | CNA (amd.com) |
| CVSS 3.1 | 8.2 | High | NVD |
Official description
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.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Out-of-bounds Write
The product writes data past the end, or before the beginning, of the intended buffer.
How developers prevent this class of flaw
- Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, many languages that perform their own memory management, such as Java and Perl, are not subject to buffer overflows. Other languages, such as Ada and C#, typically provide overflow protection, but the protection can be disabled by the programmer. Be wary that a language's interface to native code may still be subject to overflows, even if the language itself is theoretically safe.
- Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. Examples include the Safe C String Library (SafeStr) by Messier and Viega, and the Strsafe.h library from Microsoft. These libraries provide safer versions of overflow-prone string-handling functions.
- Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index checking. D3-SFCV (Stack Frame Canary Validation) from D3FEND discusses canary-based detection in detail.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Other vulnerabilities in AMD Athlon™ 3000 Series Desktop Processors with Radeon™ Graphics
- 7.4 High severity
- 8.5 High severity
- 7.5 High severity
- 7.5 High severity
- 8.2 High severity
Recent Out-of-bounds Write vulnerabilities
- 9.8 Critical severity
- 9.8 Critical severity
- 9.8 Critical severity
- 9.8 Critical severity
- 9.8 Critical severity
- 8.8 High severity
Spotted an error? Tell us.