CVE-2021-26354: Insufficient bounds checking in ASP may allow an attacker to issue a system call from a compromised ABL which may cause arbitrary memory…
Noroxi assessment
Priority: Monitor (action score 22/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.17% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. 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
Insufficient bounds checking in ASP may allow an attacker to issue a system call from a compromised ABL which may cause arbitrary memory values to be initialized to zero, potentially leading to a loss of integrity.
- Published
- May 9, 2023
- Updated
- Jun 16, 2026
- EPSS
- 0.1% · 7th percentile
- CWE
- CWE-120
Report tools
Action score
22
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
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.
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 | epyc 7773x firmware | cpe:2.3:o:amd:epyc_7773x_firmware |
| amd | epyc 7773x | cpe:2.3:h:amd:epyc_7773x |
| amd | epyc 7763 firmware | cpe:2.3:o:amd:epyc_7763_firmware |
| amd | epyc 7763 | cpe:2.3:h:amd:epyc_7763 |
| amd | epyc 7713p firmware | cpe:2.3:o:amd:epyc_7713p_firmware |
| amd | epyc 7713p | cpe:2.3:h:amd:epyc_7713p |
| amd | epyc 7713 firmware | cpe:2.3:o:amd:epyc_7713_firmware |
| amd | epyc 7713 | cpe:2.3:h:amd:epyc_7713 |
| amd | epyc 7663 firmware | cpe:2.3:o:amd:epyc_7663_firmware |
| amd | epyc 7663 | cpe:2.3:h:amd:epyc_7663 |
| amd | epyc 7643 firmware | cpe:2.3:o:amd:epyc_7643_firmware |
| amd | epyc 7643 | cpe:2.3:h:amd:epyc_7643 |
and 188 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 2nd Gen AMD EPYC™ Processors
- variousaffected
AMD 2nd Gen AMD Ryzen™ Threadripper™ Processors “Colfax”
- variousaffected
AMD 3rd Gen AMD EPYC™ Processors
- variousaffected
AMD 3rd Gen AMD Ryzen™ Threadripper™ Processors “Castle Peak” HEDT
- variousaffected
AMD AMD Ryzen™ 5000 Series Desktop Processors “Vermeer” AM4
- variousaffected
AMD Athlon™ 3000 Series Mobile Processors with Radeon™ Graphics “Pollock”
- variousaffected
AMD Athlon™ 3000 Series Mobile Processors with Radeon™ Graphics “Dali”/”Dali” ULP
- variousaffected
AMD Ryzen™ 2000 Series Desktop Processors “Pinnacle Ridge”
- variousaffected
AMD Ryzen™ 2000 series Desktop Processors “Raven Ridge” AM4
- variousaffected
AMD Ryzen™ 2000 Series Mobile Processors “Raven Ridge” FP5
- variousaffected
AMD Ryzen™ 3000 Series Desktop Processors “Matisse” AM4
- variousaffected
AMD Ryzen™ 3000 Series Mobile processor, 2nd Gen AMD Ryzen™ Mobile Processors with Radeon™ Graphics “Picasso”
- variousaffected
Affected versions · NVD (20)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- amd amd 3015ce firmwarebefore pollockpi-ft5_1.0.0.3
- amd amd 3015e firmwarebefore pollockpi-ft5_1.0.0.3
- amd epyc 7002 firmwarebefore romepi_1.0.0.d
- amd epyc 7003 firmwarebefore milanpi_1.0.0.6
- amd epyc 7232p firmwarebefore romepi_1.0.0.d
- amd epyc 7252 firmwarebefore romepi_1.0.0.d
- amd epyc 7262 firmwarebefore romepi_1.0.0.d
- amd epyc 7272 firmwarebefore romepi_1.0.0.d
- amd epyc 7282 firmwarebefore romepi_1.0.0.d
- amd epyc 72f3 firmwarebefore milanpi_1.0.0.6
- amd epyc 7302 firmwarebefore romepi_1.0.0.d
- amd epyc 7302p firmwarebefore romepi_1.0.0.d
- amd epyc 7313 firmwarebefore milanpi_1.0.0.6
- amd epyc 7313p firmwarebefore milanpi_1.0.0.6
- amd epyc 7343 firmwarebefore milanpi_1.0.0.6
- amd epyc 7352 firmwarebefore romepi_1.0.0.d
- amd epyc 7373x firmwarebefore milanpi_1.0.0.6
- amd epyc 73f3 firmwarebefore milanpi_1.0.0.6
- amd epyc 7402 firmwarebefore romepi_1.0.0.d
- amd epyc 7402p firmwarebefore romepi_1.0.0.d
Same product
amd: all recordsOther highest-scoring records for the same primary product.
- CVE-2023-31346Failure to initialize
memory in SEV Firmware may allow a privileged attacker to access stale data
from other guests.24Monitor
- CVE-2021-26371A compromised or malicious ABL or UApp could
send a SHA256 system call to the bootloader, which may result in exposure of
ASP memory to…22Monitor
- CVE-2023-31347Due to a code bug in
Secure_TSC, SEV firmware may allow an attacker with high privileges to cause a
guest to observe an incorrect TSC when…19Monitor
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.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- high · data or configuration can be modified
- Availability
- none
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- High
- Availability impact
- None
Weakness class (CWE)
CWE-120 · Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
nvd-primary
Root cause
When data is copied, the source length is not compared with the size of the destination buffer. Excess data overwrites adjacent memory.
The bug in code
The whole CWE-120 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
char buf[256];
memcpy(buf, pkt->data, pkt->len);Fixed
char buf[256];
if (pkt->len > sizeof(buf)) {
return -EINVAL;
}
memcpy(buf, pkt->data, pkt->len);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)
- Buffer Overflow via Environment VariablesCAPEC-10likelihood: High · High
- Overflow BuffersCAPEC-100likelihood: High · Very High
- Client-side Injection-induced Buffer OverflowCAPEC-14likelihood: Medium · High
- Filter Failure through Buffer OverflowCAPEC-24likelihood: High · High
- MIME ConversionCAPEC-42likelihood: High · High
- Overflow Binary Resource FileCAPEC-44likelihood: High · Very High
- Buffer Overflow via Symbolic LinksCAPEC-45likelihood: High · High
- Overflow Variables and TagsCAPEC-46likelihood: High · High
ATT&CK techniques
—
Change log (0)
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.