LiveActive security incident?Get immediate response
CVE Record

CVE-2023-1017: TPM2.0 vulnerable to out-of-bounds write

An out-of-bounds write vulnerability exists in TPM2.0's Module Library allowing writing of a 2-byte data past the end of TPM2.0 command in the CryptParameterDecryption routine. An attacker who can successfully exploit this vulnerability can lead to denial of service (crashing the TPM chip/process or rendering it unusable) and/or arbitrary code execution in the TPM context.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2023-1017 is a memory corruption flaw in the TPM2.0 Module Library. A successful attacker could crash the TPM or run code in the TPM context, affecting systems that depend on TPM-backed boot, keys, or attestation. The provided sources do not show active exploitation.

Executive priority

Treat this as high priority for platforms where TPM trust anchors protect sensitive keys, boot integrity, or compliance controls. Business urgency depends on vendor exposure confirmation, because the public bundle does not name affected device models or active exploitation.

Technical view

The vulnerability is a CWE-787 out-of-bounds write in TPM2.0 CryptParameterDecryption, allowing a 2-byte write past the end of a TPM2.0 command. The bundle lists Trusted Computing Group TPM2.0 versions 1.19, 1.38, and 1.59 as affected. Impact includes denial of service or arbitrary code execution in the TPM context.

Likely exposure

Exposure is likely in products whose TPM firmware or TPM software stack incorporates the affected TCG TPM2.0 Module Library versions. The bundle does not identify specific OEM devices, operating systems, or cloud services, so asset-level exposure requires vendor confirmation.

Exploitation context

Exploitation requires an attacker path to deliver crafted TPM2.0 commands that reach the vulnerable decryption routine. The source bundle marks KEV as false and provides no cited evidence of active exploitation or public weaponization.

Researcher notes

The key uncertainty is product mapping. The CVE describes the vulnerable routine and affected TCG library versions, but does not enumerate downstream implementations. Validation should focus on vendor firmware provenance and advisory status, not assumptions based only on TPM2.0 presence.

Mitigation direction

  • Review TCG advisory TCGVRT0007 and CERT VU#782720 for vendor-specific guidance.
  • Check OEM TPM firmware advisories for CVE-2023-1017 applicability.
  • Apply vendor-approved TPM firmware or platform updates when available.
  • Prioritize systems relying on TPM-backed boot, keys, attestation, or disk encryption.
  • Plan compensating controls where vendors confirm no update is available.

Validation and detection

  • Inventory systems with TPM2.0 hardware or TPM software implementations.
  • Map TPM vendor, firmware, and library versions against vendor advisories.
  • Confirm whether affected TCG library versions 1.19, 1.38, or 1.59 are present.
  • Record remediation evidence, including firmware version and advisory reference.
  • Monitor CERT and TCG pages for updated vendor status.
Prepared
Confidence
medium
Sources
5

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-787: 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

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. 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-2023-1017 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

0CVSS vectors
0Timeline events
0ADP providers
5Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Trusted Computing GroupTPM2.01.59Listed
Trusted Computing GroupTPM2.01.38Listed
Trusted Computing GroupTPM2.01.19Listed
Weakness

CWE details

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

CWE-787 · source CWE mapping

Out-of-bounds Write

Out-of-bounds Write represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.