dbcve.org
UnzooApplication

CVE-2015-1845

HIGH · 10.0 CVSS v2.0 Published 2015-05-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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
Buffer overflow in the EntrReadArch function in unzoo might allow remote attackers to execute arbitrary code via unspecified vectors.

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

A buffer overflow vulnerability exists in the EntrReadArch function of the unzoo utility. This flaw could allow an attacker to overwrite memory boundaries and execute arbitrary code by providing specially crafted input to the unzoo program.

MitigationRestrict access to unzoo and avoid processing untrusted zoo archive files until a patched version is available. Consider input validation and bounds checking in the EntrReadArch function.

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
UnzooApplication
Affected:all versions

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
Low
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:N/C:C/I:C/A:C

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. Locate unzoo binary on the system
    Run 'which unzoo' or 'find / -name unzoo -type f 2>/dev/null' to find if the unzoo executable exists
    Affected if The unzoo binary is found on the system - all versions are affected by this vulnerability
  2. Verify unzoo version
    Run 'unzoo --version' or 'unzoo -v' to check the installed version number
    Affected if Any version is returned - the CVE states all versions are affected
  3. Check if unzoo has execution permissions
    Run 'ls -la [path to unzoo]' to see file permissions
    Affected if The file has execute permissions, meaning it can be run and the buffer overflow can be triggered
  4. Identify processes using unzoo
    Run 'ps aux | grep unzoo' to check if unzoo is currently running
    Affected if Unzoo is actively running and processing files, making it vulnerable to exploitation
  5. Review file access to unzoo binary
    Check file ownership and permissions with 'stat [path to unzoo]'
    Affected if Untrusted users can execute unzoo, increasing the attack surface

If the unzoo binary is present on the system with any version, the environment is affected since all versions of unzoo contain the buffer overflow in EntrReadArch.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Restrict access to unzoo and avoid processing untrusted zoo archive files until a patched version is available. Consider input validation and bounds checking in the EntrReadArch function.

Fix this in Unzoo Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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