Security readout for executives and security teams
Plain-English summary
CVE-2024-36345 is a medium-severity AMD firmware issue. A user who already has high local privileges could trigger an out-of-bounds read in AMD OverDrive’s SMM module, potentially exposing limited confidential data. This is not described as remotely exploitable and is not listed as actively exploited in KEV.
Executive priority
Treat as a planned firmware remediation item, not an emergency, unless affected systems are high-value or allow broad local administrator access. The business risk is confidentiality loss after an attacker already has elevated local control.
Technical view
AMD reports improper input validation in the AOD System Management Mode module. The CVSS 4.0 score is 4.6 with local attack vector, low complexity, high privileges required, no user interaction, and low confidentiality impact only. Affected entries include multiple AMD EPYC, Ryzen, Ryzen Threadripper, Ryzen AI, and Ryzen Embedded platforms with specified PI/firmware versions.
Likely exposure
Exposure is most relevant on systems using the affected AMD processor families and listed firmware/PI versions. Practical risk is lower because exploitation requires local high privileges. Systems where privileged users, administrators, or compromised management agents are in scope should be prioritized for review.
Exploitation context
No provided source states active exploitation, and the bundle marks KEV as false. The vulnerability is post-privilege and local, so it is more likely to matter as part of a broader compromise chain than as an initial access vector.
Researcher notes
Evidence is limited to AMD/CVE metadata in the provided bundle. The affected list is version-specific but fixed versions are not included here. Avoid assuming exploit availability or remediation details beyond AMD and OEM guidance.
Mitigation direction
- Review AMD bulletins AMD-SB-3030 and AMD-SB-4017 for official remediation guidance.
- Check system or motherboard OEM firmware updates for affected AMD platforms.
- Prioritize firmware remediation on shared workstations, developer systems, and high-value administrative endpoints.
- Restrict local administrator access where business operations allow.
- Monitor AMD and OEM advisories for updated fixed-version details.
Validation and detection
- Inventory AMD CPU model and platform firmware or PI version.
- Compare findings against the affected product and version list.
- Check whether the device vendor has released applicable BIOS or firmware updates.
- Confirm whether the system remains on an affected version after maintenance.
- Document exceptions where vendor remediation is unavailable.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-1274: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2024-36345 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 4.6 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N——AMDVulnerability scoring details
Base CVSS 4.0 score
4.6MediumVector: CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://www.amd.com/en/resources/product-security/bulletin/AMD-SB-3030.htmlCVE reference, AMD
- https://www.amd.com/en/resources/product-security/bulletin/AMD-SB-4017.htmlCVE reference, AMD
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Access Control for Volatile Memory Containing Boot Code
Improper Access Control for Volatile Memory Containing Boot Code represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.