dbcve.org
SquashfsApplication · Squashfs Project

CVE-2012-4025

MEDIUM · 6.8 CVSS v2.0 Published 2012-07-19
Fix available
A fix is available. Upgrade to after 4.2 or later.
See remediation →
77/100
Remediation priority · High
Remotely reachable No privileges 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
Integer overflow in the queue_init function in unsquashfs.c in unsquashfs in Squashfs 4.2 and earlier allows remote attackers to execute arbitrary code via a crafted block_log field in the superblock of a .sqsh file, leading to a heap-based buffer overflow.

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

Integer overflow in the queue_init function in unsquashfs.c allows remote attackers to execute arbitrary code via a crafted block_log field in the superblock of a .sqsh file. The vulnerability occurs because the block_log value is not properly validated before being used in size calculations, leading to heap-based buffer overflow.

MitigationDo not process untrusted or crafted .sqsh files with unsquashfs. Upgrade to Squashfs 4.3 or later which contains the patch for this integer overflow 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
SquashfsApplication
Affected:<= 4.2

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
Network
Complexity
M
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:M/Au:N/C:P/I:P/A:P

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. Check if unsquashfs is installed
    Run `unsquashfs -version` or check your package manager for squashfs-tools package
    Affected if The command returns a version number of 4.2 or lower, or the package is not found (meaning not installed)
  2. Verify the installed version against affected range
    Compare the version output from step 1 to the affected versions <= 4.2
    Affected if The installed version is 4.2 or any version lower than 4.2
  3. Identify if .sqsh files are being processed
    Search for .sqsh files on the system using `find / -name '*.sqsh' 2>/dev/null` and check for scripts or cron jobs that invoke unsquashfs
    Affected if The system contains .sqsh files that are processed by unsquashfs, and the unsquashfs version is <= 4.2

You are affected if unsquashfs from squashfs-tools version 4.2 or lower is installed and is used to extract contents from .sqsh files.

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.

From vendor data
Upgrade available Upgrade to a release after 4.2
Interim mitigation

Do not process untrusted or crafted .sqsh files with unsquashfs. Upgrade to Squashfs 4.3 or later which contains the patch for this integer overflow vulnerability.

Fix this in Squashfs Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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