Security readout for executives and security teams
Plain-English summary
This is a firmware-level AMD issue in System Management Mode. A local attacker who already has high privileges could read or modify a limited protected memory area, risking confidentiality or integrity. It is not described as remotely exploitable or actively exploited in the provided sources.
Executive priority
Treat this as a medium-priority firmware hygiene issue, not an emergency internet-facing exposure. Prioritize systems with sensitive workloads or broad administrator access, and fold remediation into BIOS or UEFI update cycles once vendor-specific guidance is available.
Technical view
Improper validation of the SMM communications buffer can allow an out-of-bounds read or write into a limited portion of TSEG memory. The CVSS v4 vector is local, low complexity, high privileges required, no user interaction, with low confidentiality and integrity impact and no availability impact.
Likely exposure
Exposure applies to systems with the listed AMD EPYC 4004/4005, Ryzen desktop, mobile, embedded, Threadripper, and Ryzen AI processors using the affected firmware or PI versions. The bundle provides affected version identifiers but not CPEs or a universal fixed firmware version.
Exploitation context
The provided sources do not show known active exploitation, and the CVE is not in KEV. Exploitation requires local access with high privileges, so this is most relevant after a host is already significantly compromised or where privileged users are not fully trusted.
Researcher notes
The key constraint is PR:H and AV:L, which limits standalone exploitability. The security boundary is SMM/TSEG memory handling, with limited confidentiality and integrity impact. Provided evidence does not include proof-of-concept details, active exploitation, or complete fixed-version mapping.
Mitigation direction
- Review AMD-SB-3030 and AMD-SB-4017 for platform-specific vendor guidance.
- Check OEM BIOS or UEFI update channels for affected AMD systems.
- Prioritize firmware review on servers, workstations, and managed privileged endpoints.
- Restrict local administrator or root access on affected platforms.
- Track asset firmware versions until OEM remediation status is confirmed.
Validation and detection
- Inventory AMD processor models across endpoints, servers, and embedded systems.
- Record BIOS, UEFI, AGESA, or platform firmware version identifiers.
- Compare collected versions against the affected versions in the CVE record.
- Confirm whether OEM advisories map AMD guidance to your hardware model.
- After updating, verify the firmware version changed as expected.
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-124: 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-36343 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:L/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:L/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:L/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.
Buffer Underwrite ('Buffer Underflow')
Buffer Underwrite ('Buffer Underflow') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.