dbcve.org
Optane Persistent Memory FirmwareOperating system · Intel

CVE-2023-27517

HIGH · 7.8 CVSS v3.1 Published 2024-02-14
Fix available
A fix is available. Upgrade to 01.00.00.3547 / 02.00.00.3915 or later.
See remediation →
80/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 access control in some Intel(R) Optane(TM) PMem software before versions 01.00.00.3547, 02.00.00.3915, 03.00.00.0483 may allow an athenticated 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 access control in Intel Optane PMem software allows authenticated local users to escalate privileges to higher permission levels. The vulnerability affects versions prior to 01.00.00.3547, 02.00.00.3915, and 03.00.00.0483 across three release tracks.

MitigationUpdate Intel Optane PMem software to version 01.00.00.3547, 02.00.00.3915, or 03.00.00.0483 (or later) to remediate the access control vulnerability.

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
Optane Persistent Memory FirmwareOperating system
Affected:>= 01.00.00.3072, < 01.00.00.3547>= 02.00.00.3423, < 02.00.00.3915>= 03.00.00.0302, < 03.00.00.0483

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/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 checks

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

  1. Identify Intel Optane PMem software installation
    Locate the ipmctl tool or Intel Persistent Memory software components on the system. On Linux, check common paths like /usr/bin/ipmctl or /opt/ipmctl. On Windows, check Program Files for Intel Optane PMem utilities.
    Affected if Intel Optane PMem management software is installed on the system
  2. Determine the installed firmware version
    Run the version command for the Intel PMem management tool (typically 'ipmctl show -firmware' or similar tool provided by Intel) to retrieve the current firmware version.
    Affected if The reported firmware version falls within any of these ranges: 01.00.00.3072 to 01.00.00.3546, 02.00.00.3423 to 02.00.00.3914, or 03.00.00.0302 to 03.00.00.0482
  3. Check the software release track
    Identify which release track (01.x, 02.x, or 03.x) the installed firmware belongs to by examining the version number prefix.
    Affected if The installed version belongs to an affected release track and is below the fixed version for that track
  4. Verify persistent memory modules are present
    Use the PMem management tool to enumerate installed persistent memory modules (for example, 'ipmctl show -dimm' or equivalent command) to confirm the hardware is present.
    Affected if Intel Optane PMem modules are physically installed and managed by the vulnerable software version

The system is affected if Intel Optane PMem firmware version is less than 01.00.00.3547, 02.00.00.3915, or 03.00.00.0483 depending on the release track in use.

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 01.00.00.3547 / 02.00.00.3915 / 03.00.00.0483 or later
Fixed in 01.00.00.354702.00.00.391503.00.00.0483
Interim mitigation

Update Intel Optane PMem software to version 01.00.00.3547, 02.00.00.3915, or 03.00.00.0483 (or later) to remediate the access control vulnerability.

Recommended fix High confidence

Intel Optane PMem Firmware: 01.00.00.3547 (or later for 01.xx branch), 02.00.00.3915 (or later for 02.xx branch), or 03.00.00.0483 (or later for 03.xx branch)

  1. Identify the current Intel Optane Persistent Memory Firmware version installed on the system using ipmctl or other Intel firmware management tools
  2. For firmware version 01.00.x.x: Upgrade to firmware version 01.00.00.3547 or later
  3. For firmware version 02.00.x.x: Upgrade to firmware version 02.00.00.3915 or later
  4. For firmware version 03.00.x.x: Upgrade to firmware version 03.00.00.0483 or later
  5. Follow Intel's standard firmware update procedures for Optane PMem, which typically requires system downtime and proper shutdown sequence
  6. After upgrade, verify the firmware version has been successfully applied
Caveat Firmware updates to Intel Optane PMem typically require system downtime and proper shutdown procedures; ensure data backup and proper planning before applying update

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

Fix this in Optane Persistent Memory Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,920
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-27517 — 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-27517 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