CVE-2023-31102
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 · uneditedPpmd7.c in 7-Zip before 23.00 allows an integer underflow and invalid read operation via a crafted 7Z archive.
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 confidencePpmd7.c in 7-Zip before version 23.00 contains an integer underflow vulnerability that leads to an invalid read operation when decompressing specially crafted 7Z archives using the PPMd algorithm. An attacker can exploit this by delivering a malicious archive to trigger the underflow and read memory outside allocated buffers.
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< 22.01all versionsall 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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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 installed 7-Zip version on WindowsOpen Command Prompt and run: '7z' or check Program Files for 7-Zip folder, or run 'reg query "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\7-Zip" /v DisplayVersion'Affected if The installed version is earlier than 22.01 (or 23.00 per vendor advisory)
-
Identify installed 7-Zip version on Linux/UnixRun '7z --help' or '7zz --help' or check package manager: 'dpkg -l | grep -i 7zip' or 'rpm -qa | grep -i 7zip'Affected if The installed version is earlier than 22.01 (or 23.00 per vendor advisory)
-
Check NetApp Active IQ Unified Manager for versionAccess the product UI or run: 'about' command in the CLI, or check installed packages for 7-Zip componentAffected if The product is running any version (all versions affected per advisory)
-
Check NetApp Oncommand Workflow Automation for versionAccess the product UI or check installed software components for bundled 7-ZipAffected if The product is running any version (all versions affected per advisory)
-
Determine if PPMd compression method is in useInspect any 7Z archive headers using: '7z l -slt archive.7z' and look for 'Method: PPMD' or similar in the outputAffected if The archive was created using PPMd method and 7-Zip version is vulnerable
You are affected if 7-Zip version is lower than 22.01 (or 23.00 per official vendor range) OR any NetApp Active IQ Unified Manager or Oncommand Workflow Automation installation is present, and you handle 7Z archives using the PPMd algorithm.
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 · scoped22.01
Upgrade to 7-Zip version 23.00 or later. Until patched, avoid opening 7Z archives from untrusted sources as they may contain specially crafted payloads designed to trigger this vulnerability.
7-Zip version 23.00 or later
- 1. Inventory all systems with 7-Zip installed to identify versions prior to 23.00
- 2. Download 7-Zip version 23.00 or later from the official source (www.7-zip.org)
- 3. Uninstall existing 7-Zip instances on affected workstations/servers
- 4. Install the updated 7-Zip version 23.00 or later on all identified systems
- 5. For NetApp Active IQ Unified Manager and Oncommand Workflow Automation products, monitor vendor security advisories (security.netapp.com) for product-specific patches since these contain vulnerable 7-Zip code
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-31102 — 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-31102 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