dbcve.org
Tdx ModulePlugin / extension · Intel

CVE-2023-45745

HIGH · 8.2 CVSS v3.1 Published 2024-05-16
Fix available
A fix is available. Upgrade to 1.5.05.46.698 or later.
See remediation →
84/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Improper input validation in some Intel(R) TDX module software before version 1.5.05.46.698 may allow a privileged user to potentially enable escalation of privilege via local access.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Improper input validation in Intel TDX module software before version 1.5.05.46.698 allows a privileged local user to escalate privileges. TDX (Trust Domain Extensions) provides hardware-based isolation for confidential computing; the input validation flaw enables a privileged attacker to potentially elevate their privileges beyond intended boundaries within the TDX environment.

MitigationUpgrade Intel TDX module software to version 1.5.05.46.698 or later via BIOS/firmware update from the hardware vendor, and verify TDX functionality post-update.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Tdx ModulePlugin / extension
Affected:< 1.5.05.46.698
Hci Compute Node BiosOperating system
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
High
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Intel TDX is present and enabled
    Check system BIOS/UEFI settings or system information utilities for Intel TDX (Trust Domain Extensions) capability and enablement status. TDX is typically listed under CPU or security settings.
    Affected if Intel TDX is present and enabled in the system configuration
  2. Identify Intel TDX module software version
    Retrieve the Intel TDX module version from system BIOS/firmware information, typically found in the BIOS revision, firmware version, or under Intel-specific management interfaces. The version format appears as a numeric build number.
    Affected if The TDX module version cannot be determined or is listed as present
  3. Compare TDX version against the fixed release
    Compare the installed TDX module version to 1.5.05.46.698. If the version number is lower than 1.5.05.46.698, the system is running a vulnerable version.
    Affected if Installed TDX version is less than 1.5.05.46.698
  4. Identify Netapp HCI Compute Node
    Verify whether the system is a Netapp HCI Compute Node by checking the system model, product name, or hardware inventory.
    Affected if The system is a Netapp HCI Compute Node (all versions are affected)

The environment is affected if Intel TDX module version is present and below 1.5.05.46.698, or if the system is a Netapp HCI Compute Node (all versions).

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.5.05.46.698 or later
Fixed in 1.5.05.46.698
Interim mitigation

Upgrade Intel TDX module software to version 1.5.05.46.698 or later via BIOS/firmware update from the hardware vendor, and verify TDX functionality post-update.

Recommended fix High confidence

Intel TDX module software version 1.5.05.46.698 or later

  1. Identify the current version of the Intel(R) TDX module software installed on the affected system
  2. Obtain the updated Intel TDX module software version 1.5.05.46.698 or later from Intel's official support channels
  3. Follow Intel's documented upgrade procedure for TDX module software, which typically requires system downtime
  4. Verify the upgrade was successful by confirming the new TDX module version is 1.5.05.46.698 or higher
  5. For HCI Compute Node Bios: contact the system vendor (NetApp/Intel) for bios updates, as the advisory indicates all versions are affected
Caveat TDX module updates may require system reboot and could have compatibility requirements with hypervisor versions; coordinate maintenance window with infrastructure team

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Tdx Module Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-45745 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-45745 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data