CVE-2023-20526: Insufficient input validation in the ASP Bootloader may enable a privileged attacker with physical access to expose the contents of ASP…
Noroxi assessment
Priority: Monitor (action score 18/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.35% (FIRST EPSS).
- Physical access to the device is required. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: kernel-firmware (openSUSE:Leap 15.5) 20230724-150500.3.9.1; kernel-firmware (openSUSE:Leap Micro 5.3) 20220509-150400.4.25.1; kernel-firmware (openSUSE:Tumbleweed) 20231128-1.1.
- Severity is disputed: the assigning authority (CNA) scores it 1.9, NVD 4.6.
Low priority for now. Upgrade to kernel-firmware (openSUSE:Leap 15.5) 20230724-150500.3.9.1; kernel-firmware (openSUSE:Leap Micro 5.3) 20220509-150400.4.25.1; kernel-firmware (openSUSE:Tumbleweed) 20231128-1.1 or later.
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 in the ASP Bootloader may enable a privileged attacker with physical access to expose the contents of ASP memory potentially leading to a loss of confidentiality.
- Published
- Nov 14, 2023
- Updated
- Jun 17, 2026
- EPSS
- 0.3% · 29th percentile
- CWE
- —
Report tools
Action score
18
Low priority for now.
- CVSS
- 18 / 40 · 4.6 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
CNA vs NVD score
- NVD
- 4.6
- CNA · AMD
- 1.9
- 2.7 point gap
CVSS:3.1/AV:P/AC:H/PR:H/UI:N/S:C/C:L/I:N/A:N
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
- A fix has been released
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 | epyc 7001 firmware | cpe:2.3:o:amd:epyc_7001_firmware |
| amd | epyc 7001 | cpe:2.3:h:amd:epyc_7001 |
| amd | epyc 7251 firmware | cpe:2.3:o:amd:epyc_7251_firmware |
| amd | epyc 7251 | cpe:2.3:h:amd:epyc_7251 |
| amd | epyc 7261 firmware | cpe:2.3:o:amd:epyc_7261_firmware |
| amd | epyc 7261 | cpe:2.3:h:amd:epyc_7261 |
| amd | epyc 7281 firmware | cpe:2.3:o:amd:epyc_7281_firmware |
| amd | epyc 7281 | cpe:2.3:h:amd:epyc_7281 |
| amd | epyc 7301 firmware | cpe:2.3:o:amd:epyc_7301_firmware |
| amd | epyc 7301 | cpe:2.3:h:amd:epyc_7301 |
| amd | epyc 7351 firmware | cpe:2.3:o:amd:epyc_7351_firmware |
| amd | epyc 7351 | cpe:2.3:h:amd:epyc_7351 |
and 134 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 1st Gen AMD EPYC™ Processors
- variousaffected
AMD 2nd Gen AMD EPYC™ Processors
- variousaffected
AMD 3rd Gen AMD EPYC™ Processors
- variousaffected
AMD AMD EPYC™ Embedded 3000
- variousaffected
AMD AMD EPYC™ Embedded 7002
- variousaffected
AMD AMD EPYC™ Embedded 7003
- variousaffected
AMD AMD Ryzen™ Threadripper™ 2000 Series Processors “Colfax”
- 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 epyc 7001 firmwarebefore naplespi_1.0.0.h
- amd epyc 7203 firmwarebefore milanpi_1.0.0.5
- amd epyc 7203p firmwarebefore milanpi_1.0.0.5
- amd epyc 7232p firmwarebefore romepi_1.0.0.d
- amd epyc 7251 firmwarebefore naplespi_1.0.0.h
- amd epyc 7252 firmwarebefore romepi_1.0.0.d
- amd epyc 7261 firmwarebefore naplespi_1.0.0.h
- amd epyc 7262 firmwarebefore romepi_1.0.0.d
- amd epyc 7272 firmwarebefore romepi_1.0.0.d
- amd epyc 7281 firmwarebefore naplespi_1.0.0.h
- amd epyc 7282 firmwarebefore romepi_1.0.0.d
- amd epyc 72f3 firmwarebefore milanpi_1.0.0.5
- amd epyc 7301 firmwarebefore naplespi_1.0.0.h
- amd epyc 7302 firmwarebefore romepi_1.0.0.d
- amd epyc 7302p firmwarebefore romepi_1.0.0.d
- amd epyc 7303 firmwarebefore milanpi_1.0.0.5
- amd epyc 7303p firmwarebefore milanpi_1.0.0.5
- amd epyc 7313 firmwarebefore milanpi_1.0.0.5
- amd epyc 7313p firmwarebefore milanpi_1.0.0.5
- amd epyc 7343 firmwarebefore milanpi_1.0.0.5
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| openSUSE:Leap 15.5 | kernel-firmware | before 20230724-150500.3.9.1 | 20230724-150500.3.9.1 |
| openSUSE:Leap Micro 5.3 | kernel-firmware | before 20220509-150400.4.25.1 | 20220509-150400.4.25.1 |
| openSUSE:Tumbleweed | kernel-firmware | before 20231128-1.1 | 20231128-1.1 |
| openSUSE:Tumbleweed | kernel-firmware-ath12k | before 20250206-1.1 | 20250206-1.1 |
| SUSE:Linux Enterprise High Performance Computing 15 SP1-LTSS | kernel-firmware | before 20200107-150100.3.40.1 | 20200107-150100.3.40.1 |
| SUSE:Linux Enterprise High Performance Computing 15 SP3-ESPOS | kernel-firmware | before 20210208-150300.4.19.1 | 20210208-150300.4.19.1 |
| SUSE:Linux Enterprise Micro 5.3 | kernel-firmware | before 20220509-150400.4.25.1 | 20220509-150400.4.25.1 |
| SUSE:Linux Enterprise Micro 5.5 | kernel-firmware | before 20230724-150500.3.9.1 | 20230724-150500.3.9.1 |
| SUSE:Linux Enterprise Server 12 SP5 | kernel-firmware | before 20190618-5.34.1 | 20190618-5.34.1 |
Same product
amd: all recordsOther highest-scoring records for the same primary product.
- CVE-2021-26340A malicious hypervisor in conjunction with an unprivileged attacker process inside an SEV/SEV-ES guest VM may fail to flush the Translation…33Monitor
- CVE-2021-46774Insufficient DRAM address validation in System
Management Unit (SMU) may allow an attacker to read/write from/to an invalid
DRAM address…30Monitor
- CVE-2020-12988A potential denial of service (DoS) vulnerability exists in the integrated chipset that may allow a malicious attacker to hang the system…30Monitor
Published before and after this one in the same product
- ← EarlierCVE-2021-26356May 9, 2023 · A TOCTOU in ASP bootloader may allow an attacker
to tamper with the SPI ROM following data read to memory potentially resulting
in S3 data…29Monitor
- ← EarlierCVE-2023-20521Nov 14, 2023 · TOCTOU in the ASP Bootloader may allow an attacker with physical access to tamper with SPI ROM records after memory content verification…22Monitor
- Later →CVE-2023-20592Nov 14, 2023 · Improper or unexpected behavior of the INVD instruction in some AMD CPUs may allow an attacker with a malicious hypervisor to affect cache…26Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| opensuse:kernel-firmware | 20230724-150500.3.9.1 · openSUSE:Leap 15.5 | Package registry (OSV) |
| opensuse:kernel-firmware-ath12k | 20250206-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| suse:kernel-firmware | 20210208-150300.4.19.1 · SUSE:Linux Enterprise High Performance Computing 15 SP3-ESPOS | Package registry (OSV) |
| suse:kernel-firmware | 20230724-150500.3.9.1 · SUSE:Linux Enterprise Micro 5.5 | Package registry (OSV) |
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
- Physical access to the device is required.
- 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
- none
- Availability
- none
- Attack vector
- Physical
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/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.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.