Debug Exception Delivery in Secure Nested Paging
Noroxi assessment
Priority: Monitor (action score 12/100)
- Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.28% (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
A privileged attacker can prevent delivery of debug exceptions to SEV-SNP guests potentially resulting in guests not receiving expected debug information.
- Published
- Jan 11, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 20th percentile
- CWE
- CWE-693
Report tools
Action score
12
Monitor
Low priority for now.
- CVSS
- 12 / 40 · 3.2 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
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
- Proof of concept exists, no weaponized module
- 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 |
|---|---|---|
| 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 7663p firmware | cpe:2.3:o:amd:epyc_7663p_firmware |
| amd | epyc 7663p | cpe:2.3:h:amd:epyc_7663p |
| amd | epyc 7663 firmware | cpe:2.3:o:amd:epyc_7663_firmware |
| amd | epyc 7663 | cpe:2.3:h:amd:epyc_7663 |
| amd | epyc 7643p firmware | cpe:2.3:o:amd:epyc_7643p_firmware |
| amd | epyc 7643p | cpe:2.3:h:amd:epyc_7643p |
and 118 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- amd epyc 7203 firmwareall versions
- amd epyc 7203p firmwareall versions
- amd epyc 72f3 firmwareall versions
- amd epyc 7303 firmwareall versions
- amd epyc 7303p firmwareall versions
- amd epyc 7313 firmwareall versions
- amd epyc 7313p firmwareall versions
- amd epyc 7343 firmwareall versions
- amd epyc 7373x firmwareall versions
- amd epyc 73f3 firmwareall versions
- amd epyc 7413 firmwareall versions
- amd epyc 7443 firmwareall versions
- amd epyc 7443p firmwareall versions
- amd epyc 7453 firmwareall versions
- amd epyc 7473x firmwareall versions
- amd epyc 74f3 firmwareall versions
- amd epyc 7513 firmwareall versions
- amd epyc 7543 firmwareall versions
- amd epyc 7543p firmwareall versions
- amd epyc 7573x firmwareall versions
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 3rd Gen AMD EPYC™ Processors
- variousaffected
AMD 4th Gen AMD EPYC™ Processors
- Variousaffected
Same product
amd: all recordsOther highest-scoring records for the same primary product.
- CVE-2021-46771Insufficient validation of addresses in AMD Secure Processor (ASP) firmware system call may potentially lead to arbitrary code execution by 31Monitor
- CVE-2021-26353Failure to validate inputs in SMM may allow an attacker to create a mishandled error leaving the DRTM UApp in a partially initialized state 31Monitor
- CVE-2021-26324A bug with the SEV-ES TMR may lead to a potential loss of memory integrity for SNP-active VMs.31Monitor
Published before and after this one in the same product
- ← EarlierCVE-2021-26348May 11, 2022 · Failure to flush the Translation Lookaside Buffer (TLB) of the I/O memory management unit (IOMMU) may lead an IO device to write to memory i22Monitor
- ← EarlierCVE-2021-26349May 11, 2022 · Failure to assign a new report ID to an imported guest may potentially result in an SEV-SNP guest VM being tricked into trusting a dishonest22Monitor
- ← EarlierCVE-2023-20566Nov 14, 2023 · Improper address validation in ASP with SNP enabled may potentially allow an attacker to compromise guest memory integrity.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
Proof of concept available
A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.
Evidence
- Proof-of-concept repository on GitHub ×1
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Proof-of-concept repository on GitHub | stars:6 | 2023-03-11 |
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.
- First PoC-306 d
- Published
- TodayOct 21, 2026+1014 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
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.
No nightly-computed relations.
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).
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
- none
- Integrity
- low · data or configuration can be modified
- Availability
- none
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
- None
- Integrity impact
- Low
- Availability impact
- None
Weakness class (CWE)
CWE-693 · Protection Mechanism FailureCVSS vector
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:N/I:L/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)
- Accessing Functionality Not Properly Constrained by ACLsCAPEC-1likelihood: High · High
- Cross Site TracingCAPEC-107likelihood: Medium · Very High
- Directory IndexingCAPEC-127likelihood: High · Medium
- Using Malicious FilesCAPEC-17likelihood: High · Very High
- Encryption Brute ForcingCAPEC-20likelihood: Low · Low
- Exploiting Trust in ClientCAPEC-22likelihood: High · High
- Escaping a Sandbox by Calling Code in Another LanguageCAPEC-237likelihood: Low · Very High
- Using Unpublished Interfaces or FunctionalityCAPEC-36likelihood: Medium · High
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.