CVE-2022-23821: Improper access control in System Management Mode (SMM) may allow an attacker to write to SPI ROM potentially leading to arbitrary code…
Noroxi assessment
Priority: Monitor (action score 39/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: 1% (FIRST EPSS); higher than 65.4% of all records.
- 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
Improper access control in System Management Mode (SMM) may allow an attacker to write to SPI ROM potentially leading to arbitrary code execution.
- Published
- Nov 14, 2023
- Updated
- Jun 17, 2026
- EPSS
- 1.0% · 65th percentile
- CWE
- —
Report tools
Action score
39
Low priority for now.
- CVSS
- 39 / 40 · 9.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.0%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- total
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 | ryzen 9 3900 firmware | cpe:2.3:o:amd:ryzen_9_3900_firmware |
| amd | ryzen 9 3900 | cpe:2.3:h:amd:ryzen_9_3900 |
| amd | ryzen 9 3900x firmware | cpe:2.3:o:amd:ryzen_9_3900x_firmware |
| amd | ryzen 9 3900x | cpe:2.3:h:amd:ryzen_9_3900x |
| amd | ryzen 9 3900xt firmware | cpe:2.3:o:amd:ryzen_9_3900xt_firmware |
| amd | ryzen 9 3900xt | cpe:2.3:h:amd:ryzen_9_3900xt |
| amd | ryzen 9 3950x firmware | cpe:2.3:o:amd:ryzen_9_3950x_firmware |
| amd | ryzen 9 3950x | cpe:2.3:h:amd:ryzen_9_3950x |
| amd | ryzen 7 3700x firmware | cpe:2.3:o:amd:ryzen_7_3700x_firmware |
| amd | ryzen 7 3700x | cpe:2.3:h:amd:ryzen_7_3700x |
| amd | ryzen 7 3800x firmware | cpe:2.3:o:amd:ryzen_7_3800x_firmware |
| amd | ryzen 7 3800x | cpe:2.3:h:amd:ryzen_7_3800x |
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 AMD Ryzen™ Embedded 5000
- variousaffected
AMD AMD Ryzen™ Embedded R1000
- variousaffected
AMD AMD Ryzen™ Embedded R2000
- variousaffected
AMD AMD Ryzen™ Embedded V1000
- variousaffected
AMD AMD Ryzen™ Embedded V2000
- variousaffected
AMD AMD Ryzen™ Embedded V3000
- variousaffected
AMD AMD Ryzen™ 5000 Series Processors with Radeon™ Graphics “Barcelo”
- variousaffected
AMD AMD Ryzen™ 6000 Series Processors with Radeon™ Graphics "Rembrandt"
- variousaffected
AMD AMD Ryzen™ 7030 Series Mobile Processors with Radeon™ Graphics “Barcelo-R”
- variousaffected
AMD AMD Ryzen™ 7035 Series Processors with Radeon™ Graphics “Rembrandt-R”
- variousaffected
AMD Athlon™ 3000 Series Desktop Processors with Radeon™ Graphics “Picasso” AM4
- various, variousaffected
AMD Athlon™ 3000 Series Mobile Processors with Radeon™ Graphics “Pollock”
- 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 athlon 3015ce firmwarepollockpi-ft5_1.0.0.5
- amd athlon 3015e firmwarepollockpi-ft5_1.0.0.5
- amd ryzen 3 3100 firmwarecomboam4_pi_1.0.0.9
- amd ryzen 3 3100 firmwarecomboam4_v2_pi_1.2.0.8
- amd ryzen 3 3200u firmwarepicassopi-fp5_1.0.0.e
- amd ryzen 3 3250c firmwarepicassopi-fp5_1.0.0.e
- amd ryzen 3 3250u firmwarepicassopi-fp5_1.0.0.e
- amd ryzen 3 3300u firmwarepicassopi-fp5_1.0.0.e
- amd ryzen 3 3300x firmwarecomboam4_pi_1.0.0.9
- amd ryzen 3 3300x firmwarecomboam4_v2_pi_1.2.0.8
- amd ryzen 3 3350u firmwarepicassopi-fp5_1.0.0.e
- amd ryzen 3 4300u firmwarerenoirpi-fp6_1.0.0.9
- amd ryzen 3 5100 firmwarecomboam4v2_pi_1.2.0.8
- amd ryzen 3 5125c firmwarecezannepi-fp6_1.0.0.b
- amd ryzen 3 5400u firmwarecezannepi-fp6_1.0.0.b
- amd ryzen 3 5425u firmwarecezannepi-fp6_1.0.0.b
- amd ryzen 3 7335u firmwarerembrandtpi-fp7_1.0.0.2
- amd ryzen 5 3450u firmwarepicassopi-fp5_1.0.0.e
- amd ryzen 5 3500 firmwarecomboam4_pi_1.0.0.9
- amd ryzen 5 3500 firmwarecomboam4_v2_pi_1.2.0.8
Same product
amd: all recordsOther highest-scoring records for the same primary product.
- CVE-2022-23820Failure to validate the AMD SMM communication buffer
may allow an attacker to corrupt the SMRAM potentially leading to arbitrary
code…39Monitor
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
- 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
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
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.