CVE-2021-39298: A potential vulnerability in AMD System Management Mode (SMM) interrupt handler may allow an attacker with high privileges to access the SMM…
Noroxi assessment
Priority: Monitor (action score 35/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.37% (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.
- Severity is disputed: the assigning authority (CNA) scores it 6.5, NVD 8.8.
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 potential vulnerability in AMD System Management Mode (SMM) interrupt handler may allow an attacker with high privileges to access the SMM resulting in arbitrary code execution which could be used by malicious actors to bypass security mechanisms provided in the UEFI firmware.
- Published
- Feb 16, 2022
- Updated
- Oct 7, 2026
- EPSS
- 0.3% · 31th percentile
- CWE
- CWE-269
Report tools
Action score
35
Low priority for now.
- CVSS
- 35 / 40 · 8.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 8.8
- CNA · AMD
- 6.5
- 2.3 point gap
CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:H
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
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 |
|---|---|---|
| hp | z1 entry tower g5 workstation firmware | cpe:2.3:o:hp:z1_entry_tower_g5_workstation_firmware |
| hp | z1 entry tower g5 workstation | cpe:2.3:h:hp:z1_entry_tower_g5_workstation |
| hp | z1 entry tower g6 workstation firmware | cpe:2.3:o:hp:z1_entry_tower_g6_workstation_firmware |
| hp | z1 entry tower g6 workstation | cpe:2.3:h:hp:z1_entry_tower_g6_workstation |
| hp | z1 g8 tower desktop pc firmware | cpe:2.3:o:hp:z1_g8_tower_desktop_pc_firmware |
| hp | z1 g8 tower desktop pc | cpe:2.3:h:hp:z1_g8_tower_desktop_pc |
| hp | z4 g4 workstation (core-x) firmware | cpe:2.3:o:hp:z4_g4_workstation_(core-x)_firmware |
| hp | z4 g4 workstation (core-x) | cpe:2.3:h:hp:z4_g4_workstation_(core-x) |
| hp | z4 g4 workstation (xeon w) firmware | cpe:2.3:o:hp:z4_g4_workstation_(xeon_w)_firmware |
| hp | z4 g4 workstation (xeon w) | cpe:2.3:h:hp:z4_g4_workstation_(xeon_w) |
| hp | z6 g4 workstation firmware | cpe:2.3:o:hp:z6_g4_workstation_firmware |
| hp | z6 g4 workstation | cpe:2.3:h:hp:z6_g4_workstation |
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 EPYC
- Variousaffected
AMD 3rd Gen EPYC
- variousaffected
AMD Ryzen 2000 Series
- variousaffected
AMD Ryzen 3000 Series
- Variousaffected
AMD Ryzen 5000 Series
- variousaffected
Affected versions · NVD (20)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- hp 260 g3 desktop mini pc firmwareup to 2.17.00 inclusive
- hp elite dragonfly firmwarebefore 01.12.00
- hp elite dragonfly g2 firmwarebefore 01.08.00
- hp elite dragonfly max firmwarebefore 01.08.00
- hp elite x2 1013 g3 firmwarebefore 01.19.00
- hp elite x2 g4 firmwarebefore 01.12.00
- hp elite x2 g8 tablet firmwarebefore 01.08.00
- hp elitebook 1050 g1 firmwarebefore 01.19.00
- hp elitebook 830 g5 firmwarebefore 01.19.00
- hp elitebook 830 g6 firmwarebefore 01.12.00
- hp elitebook 830 g7 firmwarebefore 01.08.00
- hp elitebook 830 g8 firmwarebefore 01.08.00
- hp elitebook 836 g5 firmwarebefore 01.19.00
- hp elitebook 836 g6 firmwarebefore 01.12.00
- hp elitebook 840 aero g8 firmwarebefore 01.08.00
- hp elitebook 840 g5 firmwarebefore 01.19.00
- hp elitebook 840 g5 healthcare edition firmwarebefore 01.19.00
- hp elitebook 840 g6 firmwarebefore 01.12.00
- hp elitebook 840 g6 healthcare edition firmwarebefore 01.12.00
- hp elitebook 840 g7 firmwarebefore 01.08.00
Same product
hp: all recordsOther highest-scoring records for the same primary product.
- CVE-2021-39301Potential vulnerabilities have been identified in UEFI firmware (BIOS) for some PC products which may allow escalation of privilege and…35Monitor
- CVE-2021-39300Potential vulnerabilities have been identified in UEFI firmware (BIOS) for some PC products which may allow escalation of privilege and…35Monitor
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
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
Impact can extend beyond the vulnerable component (scope changes).
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-269 · Improper Privilege ManagementCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
nvd-primary
Root cause
To simplify setup, a service account is granted broad, cluster-wide permissions. The principle of least privilege is skipped during installation.
The bug in code
The whole CWE-269 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
kind: ClusterRole
rules:
- apiGroups: ["*"]
resources: ["*"]
verbs: ["*"]Fixed
kind: Role
metadata:
namespace: lodos-system
rules:
- apiGroups: ["apps"]
resources: ["deployments"]
verbs: ["get", "list", "update"]Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Change log (1)
- SSVC exploitation— → none
For records you follow, these changes also arrive as notifications. →
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.