Ampereone A192-32m Firmware: Out-of-bounds Write
CVE-2025-62864 is a critical-severity out-of-bounds write vulnerability in Ampereone A192-32m Firmware from Amperecomputing, with a CVSS 3.1 base score of 9.8 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists version 5.4.5.1 as the first without the flaw, so updating Ampereone A192-32m Firmware to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.36% chance of exploitation within 30 days, which is low compared with other CVEs.
Critical severity: a successful attack would have severe impact.
What to do
- Update Ampereone A192-32m Firmware to 5.4.5.1 or a later version.
- Update Ampereone A192-26m Firmware to 5.4.5.1 or a later version.
- Update Ampereone A160-28m Firmware to 5.4.5.1 or a later version.
- Read the advisory on amperecomputing.com for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Amperecomputing | Ampereone A192-32m Firmware | before 5.4.5.1 | 5.4.5.1 |
| Amperecomputing | Ampereone A192-26m Firmware | before 5.4.5.1 | 5.4.5.1 |
| Amperecomputing | Ampereone A160-28m Firmware | before 5.4.5.1 | 5.4.5.1 |
| Amperecomputing | Ampereone A144-33m Firmware | before 5.4.5.1 | 5.4.5.1 |
| Amperecomputing | Ampereone A144-26m Firmware | before 5.4.5.1 | 5.4.5.1 |
| Amperecomputing | Ampereone A96-36m Firmware | before 5.4.5.1 | 5.4.5.1 |
| Amperecomputing | Ampereone A96-36x Firmware | before 4.4.5.2 | 4.4.5.2 |
| Amperecomputing | Ampereone A128-34x Firmware | before 4.4.5.2 | 4.4.5.2 |
| Amperecomputing | Ampereone A144-24x Firmware | before 4.4.5.2 | 4.4.5.2 |
| Amperecomputing | Ampereone A144-27x Firmware | before 4.4.5.2 | 4.4.5.2 |
| Amperecomputing | Ampereone A160-28x Firmware | before 4.4.5.2 | 4.4.5.2 |
| Amperecomputing | Ampereone A192-26x Firmware | before 4.4.5.2; before 3.5.9.3 | 4.4.5.2, 3.5.9.3 |
| Amperecomputing | Ampereone A192-32x Firmware | before 3.5.9.3 | 3.5.9.3 |
Version data comes from NVD's product matching. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- 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:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Scored by CISA (ADP).
Official description
Ampere AmpereOne AC03 devices before 3.5.9.3, AmpereOne AC04 devices before 4.4.5.2, and AmpereOne M devices before 5.4.5.1 allow an incorrectly formed SMC call to UEFI-MM MMCommunicate service that could result in an out-of-bounds write within the UEFI-MM Secure Partition context.
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: yes, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Advisories
Other vulnerabilities in Ampereone A192-32m Firmware
- 9.8 Critical severity
Recent Out-of-bounds Write vulnerabilities
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
Spotted an error? Tell us.