NVD / CVE Program· CNA AMD

CVE-2023-20563: Insufficient protections in System Management Mode (SMM) code may allow an attacker to potentially enable escalation of privilege via local

Noroxi assessment

Priority: Monitor (action score 31/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.20% (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 protections in System Management Mode (SMM) code may allow an attacker to potentially enable escalation of privilege via local access.

HighCVSS 7.8 · v3.1—No exploit No fix recorded

Local privilege escalation

Published: Nov 14, 2023
Updated: Jun 17, 2026
EPSS: 0.2% · 10th percentile
CWE: CWE-269

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 31 / 40 · 7.8 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.2%

CISA SSVC decision

Exploitation: none
Automatable: no
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.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

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 help

Affected 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.

ProductVersion

Vendor	Product	CPE
amd	ryzen 3 5100 firmware	cpe:2.3:o:amd:ryzen_3_5100_firmware
amd	ryzen 3 5100	cpe:2.3:h:amd:ryzen_3_5100
amd	ryzen 3 5300g firmware	cpe:2.3:o:amd:ryzen_3_5300g_firmware
amd	ryzen 3 5300g	cpe:2.3:h:amd:ryzen_3_5300g
amd	ryzen 3 5300ge firmware	cpe:2.3:o:amd:ryzen_3_5300ge_firmware
amd	ryzen 3 5300ge	cpe:2.3:h:amd:ryzen_3_5300ge
amd	ryzen 5 5500 firmware	cpe:2.3:o:amd:ryzen_5_5500_firmware
amd	ryzen 5 5500	cpe:2.3:h:amd:ryzen_5_5500
amd	ryzen 5 5600g firmware	cpe:2.3:o:amd:ryzen_5_5600g_firmware
amd	ryzen 5 5600g	cpe:2.3:h:amd:ryzen_5_5600g
amd	ryzen 5 5600ge firmware	cpe:2.3:o:amd:ryzen_5_5600ge_firmware
amd	ryzen 5 5600ge	cpe:2.3:h:amd:ryzen_5_5600ge

and 130 more

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

amd ryzen 3 5100 firmwarebefore comboam4v2_1.2.0.b
amd ryzen 3 5125c firmwarebefore cezannepi-fp6_1.0.0.f
amd ryzen 3 5300g firmwarebefore comboam4v2_1.2.0.b
amd ryzen 3 5300ge firmwarebefore comboam4v2_1.2.0.b
amd ryzen 3 5400u firmwarebefore cezannepi-fp6_1.0.0.f
amd ryzen 3 5425u firmwarebefore cezannepi-fp6_1.0.0.f
amd ryzen 3 7335u firmwarebefore rembrandtpi-fp7_1.0.0.9
amd ryzen 3 pro 7330u firmwarebefore cezannepi-fp6_1.0.0.f
amd ryzen 3 pro 7440u firmwarebefore phoenixpi-fp8-fp7_pi_1.0.0.1g
amd ryzen 5 5500 firmwarebefore comboam4v2_1.2.0.b
amd ryzen 5 5500h firmwarebefore cezannepi-fp6_1.0.0.f
amd ryzen 5 5560u firmwarebefore cezannepi-fp6_1.0.0.f
amd ryzen 5 5600g firmwarebefore comboam4v2_1.2.0.b
amd ryzen 5 5600ge firmwarebefore comboam4v2_1.2.0.b
amd ryzen 5 5600h firmwarebefore cezannepi-fp6_1.0.0.f
amd ryzen 5 5600hs firmwarebefore cezannepi-fp6_1.0.0.f
amd ryzen 5 5600u firmwarebefore cezannepi-fp6_1.0.0.f
amd ryzen 5 5625u firmwarebefore cezannepi-fp6_1.0.0.f
amd ryzen 5 6600h firmwarebefore rembrandtpi-fp7_1.0.0.9
amd ryzen 5 6600hs firmwarebefore rembrandtpi-fp7_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 AMD Ryzen™ Embedded 5000
- variousaffected
AMD AMD Ryzen™ Embedded R1000
- variousaffected
AMD AMD Ryzen™ Embedded R2000
- 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 Ryzen™ 5000 Series Desktop Processor with Radeon™ Graphics “Cezanne”
- variousaffected
AMD Ryzen™ 5000 Series Mobile Processors with Radeon™ Graphics “Cezanne”
- variousaffected
AMD Ryzen™ 7000 Series Desktop Processors “Raphael” XD3
- variousaffected
AMD Ryzen™ 7040 Series Mobile Processors with Radeon™ Graphics “Phoenix” FP7/FP7r2/FP8
- variousaffected

Same product

amd: all records

Other highest-scoring records for the same primary product.

CVE-2023-20571A race condition in System Management Mode (SMM) code may allow an attacker using a compromised user space to leverage CVE-2018-8897 potenti
32Monitor
CVE-2023-20565Insufficient protections in System Management Mode (SMM) code may allow an attacker to potentially enable escalation of privilege via local
31Monitor

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 researchers

Finders, 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.

CVE-2023-205650 days apartInsufficient protections in System Management Mode (SMM) code may allow an attacker to potentially enable escalation of privilege via local
31Monitor

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.
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

Attack vector: Local
Attack complexity: Low
Privileges required: Low
User interaction: None
Scope: Unchanged
Confidentiality impact: High
Integrity impact: High
Availability impact: High

Weakness class (CWE)

CWE-269 · Improper Privilege Management

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/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 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

yaml

1kind: ClusterRole
2rules:
3  - apiGroups: ["*"]
4    resources: ["*"]
5    verbs: ["*"]

Fixed

yaml

1kind: Role
2metadata:
3  namespace: lodos-system
4rules:
5  - apiGroups: ["apps"]
6    resources: ["deployments"]
7    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.

Attack patterns (CAPEC)

ATT&CK techniques

Abuse Elevation Control MechanismT1548

Change log

No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.

References

www.amd.com/en/corporate/product-security/bulletin/AMD-SB-4002

Show all references (1 more)

www.amd.com/en/corporate/product-security/bulletin/AMD-SB-5001

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records