CVE-2024-11612
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 · unedited7-Zip CopyCoder Infinite Loop Denial-of-Service Vulnerability. This vulnerability allows remote attackers to create a denial-of-service condition on affected installations of 7-Zip. Interaction with this library is required to exploit this vulnerability but attack vectors may vary depending on the implementation. The specific flaw exists within the processing of streams. The issue results from a logic error that can lead to an infinite loop. An attacker can leverage this vulnerability to create a denial-of-service condition on the system. Was ZDI-CAN-24307.
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 confidenceA logic error in 7-Zip's stream processing code creates an infinite loop condition. When processing certain streams, the vulnerability causes the application to enter an endless loop, resulting in a denial-of-service condition that hangs the process.
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>= 24.06, < 24.08CVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/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 versionOpen 7-Zip File Manager, click Help, then About 7-Zip. The version number displays in the dialog window. Alternatively, right-click the 7-Zip executable file, select Properties, and check the Details tab for version information.Affected if Version shown is 24.06, 24.07, or any version >= 24.06 but < 24.08
-
Confirm version falls within affected rangeCompare the identified version against the affected range: 7-Zip versions greater than or equal to 24.06 and less than 24.08.Affected if Installed version is >= 24.06 and < 24.08
-
Verify stream processing is in useCheck if 7-Zip is being used to extract, open, or decompress archive files. The infinite loop triggers during stream processing operations.Affected if 7-Zip processes archive files or streams, as this is the code path containing the logic error
You are affected if 7-Zip version is 24.06, 24.07, or any version from 24.06 up to but not including 24.08, and you use it to process archive streams.
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 · scoped24.08
Update 7-Zip to the latest version to patch the logic error in stream processing. If immediate patching is not possible, limit or sanitize input files processed by 7-Zip to prevent triggering the infinite loop.
7-Zip 24.08 or later
- Navigate to the official 7-Zip website (https://www.7-zip.org/)
- Download version 24.08 or later of 7-Zip for your system (32-bit or 64-bit)
- Run the downloaded installer or extract the portable version
- If using the installer: follow the installation wizard prompts to install the new version
- If updating an existing installation: you can typically install directly over the old version
- Verify the installed version by opening 7-Zip and checking Help > About to confirm version 24.08 or later is installed
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.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 $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-11612 — 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-2024-11612 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