CVE-2023-22311
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 access control in some Intel(R) Optane(TM) PMem 100 Series Management Software before version 01.00.00.3547 may allow an authenticated 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 confidenceImproper access control in Intel Optane PMem 100 Series Management Software allows an authenticated local user to escalate privileges. The vulnerability stems from insufficient authorization checks in the management software, enabling a user with standard local access to gain higher-level permissions.
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< 01.00.00.3547CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify Intel Optane PMem 100 Series hardwareRun 'ipmctl show -dimm' or check system BIOS/UEFI for Intel Optane Persistent Memory modules. Look for PMem 100 Series (formerly known as Apache Pass) in the device inventory.Affected if No Intel Optane PMem 100 Series hardware is present in the system, then the environment is not affected.
-
Check PMem firmware versionUse the ipmctl command: 'ipmctl show -dimm -firmware' or 'ipmctl show -dimm' to display firmware version information for each PMem module. Note the firmware version listed.Affected if The installed firmware version is lower than 01.00.00.3547 (for example, 01.00.00.3500 or earlier).
-
Verify management software is in useConfirm Intel Optane PMem Management Software (ipmctl or similar) is installed and available on the system. Check with 'ipmctl version' or locate the ipmctl binary.Affected if The management software is not installed or not in use, the specific privilege escalation vector may not apply, though the firmware remains vulnerable.
A system is affected if it contains Intel Optane PMem 100 Series hardware with firmware version prior to 01.00.00.3547 and has the Intel Optane PMem management software installed and accessible to local authenticated users.
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.
dbcve · scoped01.00.00.3547
Upgrade Intel Optane PMem 100 Series Management Software to version 01.00.00.3547 or later to remediate the improper access control vulnerability.
01.00.00.3547
- Upgrade Intel Optane PMem 100 Series Management Software to version 01.00.00.3547 or later
- Verify the installed version matches or exceeds the fixed release after upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation5.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,936.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-22311 — 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-22311 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