CVE-2023-47855
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 · uneditedImproper 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 · high confidenceIntel TDX (Trust Domain Extensions) module software contains an improper input validation vulnerability that could allow a privileged user to escalate their privileges via local access. This affects versions prior to 1.5.05.46.698.
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< 1.5.05.46.698all versionsCVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/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 checksWork through these to decide whether this CVE applies to you.
-
Verify Intel TDX is enabled on the systemCheck system firmware/BIOS settings or use platform-specific tools (such as dmidecode, tdx-tool, or platform management interfaces) to confirm Intel TDX virtualization extension is activeAffected if Intel TDX is enabled and the TDX module version cannot be determined or is below 1.5.05.46.698
-
Determine the installed Intel TDX module software versionUse Intel platform management tools, system firmware interfaces, or consult system vendor documentation to retrieve the TDX module version numberAffected if The installed version is less than 1.5.05.46.698 or cannot be verified
-
Identify the Netapp HCI Compute Node modelCheck system inventory or hardware documentation to determine if the system is a Netapp HCI Compute NodeAffected if The system is a Netapp HCI Compute Node with any BIOS version listed (all versions are affected)
-
Check Netapp HCI Compute Node BIOS versionAccess BMC/IPMI or Netapp management interfaces to retrieve the current BIOS firmware versionAffected if Running any BIOS version on a Netapp HCI Compute Node (since all versions are affected)
A system is affected if Intel TDX is enabled with a TDX module version prior to 1.5.05.46.698, or if it is a Netapp HCI Compute Node running any BIOS version.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor data1.5.05.46.698
Update Intel TDX module software to version 1.5.05.46.698 or later. Due to the privileged nature of the component and potential impact on confidential VMs, test thoroughly in a staging environment before production deployment.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-47855 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-47855 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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