CVE-2022-23818: Insufficient input validation on the model specific register: VM_HSAVE_PA may potentially lead to loss of SEV-SNP guest memory integrity.
Noroxi assessment
Priority: Monitor (action score 30/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.50% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- 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 input validation on the model specific register: VM_HSAVE_PA may potentially lead to loss of SEV-SNP guest memory integrity.
- Published
- May 9, 2023
- Updated
- Jun 17, 2026
- EPSS
- 0.5% · 43th percentile
- CWE
- CWE-20
Report tools
Action score
30
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.5%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- 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.
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 72f3 firmware | cpe:2.3:o:amd:epyc_72f3_firmware |
| amd | epyc 72f3 | cpe:2.3:h:amd:epyc_72f3 |
| amd | epyc 7313 firmware | cpe:2.3:o:amd:epyc_7313_firmware |
| amd | epyc 7313 | cpe:2.3:h:amd:epyc_7313 |
| amd | epyc 7313p firmware | cpe:2.3:o:amd:epyc_7313p_firmware |
| amd | epyc 7313p | cpe:2.3:h:amd:epyc_7313p |
| amd | epyc 7343 firmware | cpe:2.3:o:amd:epyc_7343_firmware |
| amd | epyc 7343 | cpe:2.3:h:amd:epyc_7343 |
| amd | epyc 7373x firmware | cpe:2.3:o:amd:epyc_7373x_firmware |
| amd | epyc 7373x | cpe:2.3:h:amd:epyc_7373x |
| amd | epyc 73f3 firmware | cpe:2.3:o:amd:epyc_73f3_firmware |
| amd | epyc 73f3 | cpe:2.3:h:amd:epyc_73f3 |
and 34 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- amd epyc 72f3 firmwaremilanpi_1.0.0.9
- amd epyc 7313 firmwaremilanpi_1.0.0.9
- amd epyc 7313p firmwaremilanpi_1.0.0.9
- amd epyc 7343 firmwaremilanpi_1.0.0.9
- amd epyc 7373x firmwaremilanpi_1.0.0.9
- amd epyc 73f3 firmwaremilanpi_1.0.0.9
- amd epyc 7413 firmwaremilanpi_1.0.0.9
- amd epyc 7443 firmwaremilanpi_1.0.0.9
- amd epyc 7443p firmwaremilanpi_1.0.0.9
- amd epyc 7453 firmwaremilanpi_1.0.0.9
- amd epyc 7473x firmwaremilanpi_1.0.0.9
- amd epyc 74f3 firmwaremilanpi_1.0.0.9
- amd epyc 7513 firmwaremilanpi_1.0.0.9
- amd epyc 7543 firmwaremilanpi_1.0.0.9
- amd epyc 7543p firmwaremilanpi_1.0.0.9
- amd epyc 7573x firmwaremilanpi_1.0.0.9
- amd epyc 75f3 firmwaremilanpi_1.0.0.9
- amd epyc 7643 firmwaremilanpi_1.0.0.9
- amd epyc 7663 firmwaremilanpi_1.0.0.9
- amd epyc 7713 firmwaremilanpi_1.0.0.9
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™
- variousaffected
Same product
amd: all recordsOther highest-scoring records for the same primary product.
- CVE-2023-20520Improper access control settings in ASP
Bootloader may allow an attacker to corrupt the return address causing a
stack-based buffer overrun 39Monitor
- CVE-2021-26379Insufficient input validation of mailbox data in the
SMU may allow an attacker to coerce the SMU to corrupt SMRAM, potentially
leading to a 39Monitor
- CVE-2021-46756Insufficient validation of inputs in
SVC_MAP_USER_STACK in the ASP (AMD Secure Processor) bootloader may allow an
attacker with a malicious 36Monitor
Published before and after this one in the same product
- ← EarlierCVE-2021-46769May 9, 2023 · Insufficient syscall input validation in the ASP
Bootloader may allow a privileged attacker to execute arbitrary DMA copies,
which can lead 35Monitor
- ← EarlierCVE-2021-46775May 9, 2023 · Improper input validation in ABL may enable an
attacker with physical access, to perform arbitrary memory overwrites,
potentially leading to27Monitor
- Later →CVE-2023-20524May 9, 2023 · An attacker with a compromised ASP could
possibly send malformed commands to an ASP on another CPU, resulting in an out
of bounds write, pot30Monitor
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.
No history yet (it accumulates with the daily EPSS job).
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
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- 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
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- High
- Availability impact
- None
Weakness class (CWE)
CWE-20 · Improper Input ValidationCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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)
- Buffer Overflow via Environment VariablesCAPEC-10likelihood: High · High
- Server Side Include (SSI) InjectionCAPEC-101likelihood: High · High
- Cross Zone ScriptingCAPEC-104likelihood: Medium · High
- Command Line Execution through SQL InjectionCAPEC-108likelihood: Low · Very High
- Object Relational Mapping InjectionCAPEC-109likelihood: Low · High
- SQL Injection through SOAP Parameter TamperingCAPEC-110likelihood: High · Very High
- Double EncodingCAPEC-120likelihood: Low · Medium
- Subverting Environment Variable ValuesCAPEC-13likelihood: High · Very High
ATT&CK techniques
- Obfuscated Files or InformationT1027
- Masquerading: Invalid Code SignatureT1036.001
- Steal Web Session CookieT1539
- Subvert Trust Controls: Code SigningT1553.002
- Impair Defenses:Impair Command History LoggingT1562.003
- Hijack Execution Flow:Dynamic Linker HijackingT1574.006
- Hijack Execution Flow:Path Interception by PATH Environment VariableT1574.007
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.