LiveActive security incident?Get immediate response
CVE Record

CVE-2022-23817: Insufficient checking of memory buffer in AMD Secure Processor (ASP) Secure OS may allow an attacker with a...

Insufficient checking of memory buffer in AMD Secure Processor (ASP) Secure OS may allow an attacker with a malicious trusted application to read/write to the ASP Secure OS kernel virtual address space, potentially resulting in privilege escalation.

HighCVSS 7.3Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This is a firmware-level AMD Secure Processor issue. If an attacker can run a malicious trusted application locally, they may read or write ASP Secure OS kernel memory and escalate privileges. Business risk is concentrated on systems using listed AMD Ryzen, Athlon, Threadripper, Embedded, or Radeon RX 5000 products.

Executive priority

Treat as high priority for affected fleets, but not as an emergency internet-wide exposure based on provided evidence. Focus on asset identification, OEM patch availability, and staged firmware or software updates for systems where AMD Secure Processor compromise would materially affect business risk.

Technical view

CVE-2022-23817 is insufficient memory buffer checking in AMD Secure Processor Secure OS. The CVSS 4.0 vector indicates local access, high complexity, low privileges, and no user interaction, with high vulnerable-system confidentiality, integrity, and availability impact. CWE mappings are CWE-120 and CWE-20.

Likely exposure

Exposure is likely where affected AMD processor or Radeon RX 5000 software versions are present, especially systems that rely on ASP security boundaries. The source bundle lists many client, workstation, mobile, embedded, and graphics product families, but does not provide CPEs or asset-discovery automation.

Exploitation context

The source bundle does not show CISA KEV listing or cited evidence of active exploitation. Exploitation requires local access, low privileges, high complexity, and a malicious trusted application, so this is not described as a remote unauthenticated attack.

Researcher notes

The provided data names affected product families and versions but does not include fixed version details, exploit telemetry, or proof-of-concept evidence. Validation should stay defensive: confirm platform versions, map AMD bulletins to OEM advisories, and avoid assuming coverage from operating-system patch status alone.

Mitigation direction

  • Review the relevant AMD security bulletin for each affected product family.
  • Obtain BIOS, firmware, AGESA, or AMD Software updates from AMD or the system OEM.
  • Prioritize high-value endpoints, embedded systems, and workstations using affected AMD platforms.
  • Restrict untrusted local software and trusted-application deployment paths where operationally possible.
  • Track OEM advisory status when AMD guidance depends on platform vendor delivery.

Validation and detection

  • Inventory systems for listed AMD Ryzen, Athlon, Threadripper, Embedded, and Radeon RX 5000 products.
  • Compare BIOS, firmware, platform initialization, and AMD Software versions against AMD bulletin guidance.
  • Confirm OEM update availability and deployment status for each affected hardware model.
  • Review endpoint controls limiting local code execution and unauthorized trusted application installation.
  • Document exceptions where firmware updates are unavailable or require maintenance windows.
Prepared
Confidence
medium
Sources
6

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · low confidence lookup

CWE-120: 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 lookup
cwe · low confidence lookup

CWE-20: 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 lookup
description · low confidence lookup

Privilege behavior lookup

The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-23817 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.3 (4.0)
Known Exploited
No
Published

Vector: CVSS:4.0/AV:L/AC:H/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Official CVE source material

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.

1CVSS vectors
3Timeline events
1ADP providers
5Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total

CVSS vector scores

1 official score

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

ScoreVersionSeverityVectorExploitImpactSource
7.3CVSS 4.0HighCVSS:4.0/AV:L/AC:H/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N——AMD

Vulnerability scoring details

Base CVSS 4.0 score

7.3High
CVSS 4.0 vector shape for CVE-2022-23817Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: CVSS:4.0/AV:L/AC:H/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
AMDAMD Athlon™ 3000 Series Mobile Processors with Radeon™ GraphicsPicassoPI-FP5 1.0.0.Eaffected
AMDAMD Ryzen™ Threadripper™ PRO 3000 WX-Series ProcessorsChagallWSPI-sWRX8 1.0.0.5, CastlePeakWSPI-sWRX8 1.0.0.Aaffected
AMDAMD Ryzen™ 5000 Series Desktop Processors with Radeon™ GraphicsComboAM4v2 PI 1.2.0.8affected
AMDAMD Ryzen™ Threadripper™ PRO 5000 WX-Series ProcessorsChagallWSPI-sWRX8 1.0.0.5affected
AMDAMD Ryzen™ 4000 Series Mobile Processors with Radeon™ GraphicsRenoirPI-FP6 1.0.0.Aaffected
AMDAMD Ryzen™ 3000 Series Mobile Processors with Radeon™ GraphicsPicassoPI-FP5 1.0.0.Eaffected
AMDAMD Ryzen™ 5000 Series Mobile Processors with Radeon™ GraphicsCezannePI-FP6 1.0.0.Caffected
AMDAMD Ryzen™ 3000 Series Desktop ProcessorsComboAM4V1 1.0.0.A, ComboAM4V2 1.2.0.9affected
AMDAMD Ryzen™ 2000 Mobile ProcessorsComboAM4v2 PI 1.2.0.8, ComboAM4PI 1.0.0.9affected
AMDAMD Ryzen™ 4000 Series Desktop ProcessorsComboAM4v2 PI 1.2.0.8affected
AMDAMD Ryzen™ 5000 Series Desktop ProcessorsComboAM4v2 PI 1.2.0.8affected
AMDAMD Ryzen™ 6000 Series Processors with Radeon™ GraphicsRembrandtPI-FP7_1.0.0.5affected
AMDAMD Ryzen™ Embedded R1000 Series ProcessorsEmbeddedPI-FP5_1.2.0.Aaffected
AMDAMD Ryzen™ Embedded R2000 Series ProcessorsEmbeddedR2KPI-FP5 1.0.0.2affected
AMDAMD Ryzen™ Embedded 5000 Series ProcessorsEmbAM4PI 1.0.0.2affected
AMDAMD Ryzen™ Embedded V1000 Series Processors (formerly codenamed "Raven Ridge")EmbeddedPI-FP5_1.2.0.Aaffected
AMDAMD Ryzen™ Embedded V1000 Series Processors (formerly codenamed "Picasso")EmbeddedPI-FP5_1.2.0.Aaffected
AMDAMD Ryzen™ Embedded V2000 Series ProcessorEmbeddedPI-FP6_1.0.0.8affected
AMDAMD Ryzen™ Embedded V3000 Series ProcessorsEmbeddedPI-FP7r2_1002affected
AMDAMD Radeon™ RX 5000 Series Graphics ProductsAMD Software: Adrenalin Edition 22.5.2 (22.10.17.01)affected
AMDAMD Radeon™ PRO W5000 Series Graphics ProductsAMD Software: PRO Edition 22.Q2 (22.10.20)affected
AMDAMD Radeon™ RX 6000 Series Graphics ProductsAMD Software: Adrenalin Edition 22.5.2 (22.10.17.01)affected
AMDAMD Radeon™ PRO W6000 Series Graphics ProductsAMD Software: PRO Edition 22.Q2 (22.10.20)affected
AMDMI-25 / 50No fix plannedaffected
AMDMI-100ROCm 6.4.2affected
AMDAMD Instinct™ MI250ROCm 7.0affected
AMDAMD Instinct™ MI210ROCm 7.0affected
Weakness

CWE details

CWE-120CWE-20

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.