dbcve.org
Debian LinuxOperating system · Debian

CVE-2013-7087

CRITICAL · 9.8 CVSS v3.1 Published 2019-11-15
Fix available
A fix is available. Upgrade to 0.97.7 or later.
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
ClamAV before 0.97.7 has WWPack corrupt heap memory

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

Heap memory corruption vulnerability in ClamAV's WWPack module affecting versions prior to 0.97.7. The WWPack decompression routine improperly handles crafted files, leading to heap corruption that could enable remote code execution or denial of service.

MitigationUpgrade ClamAV to version 0.97.7 or later to remediate the vulnerability. Verify signature database updates continue to function post-upgrade.

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
Debian LinuxOperating system
Affected:= 8.0= 9.0= 10.0
FedoraOperating system
Affected:= 17= 18
ClamavApplication
Affected:< 0.97.7

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
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify ClamAV is installed
    Run 'clamd --version' or 'clamscan --version' to check if ClamAV is present on the system
    Affected if ClamAV is not installed - the system is not affected by this CVE
  2. Check installed ClamAV version
    Run 'clamd --version' and note the version number displayed (e.g., 0.97.6, 0.97.8)
    Affected if The version is less than 0.97.7 (for example, 0.97.6, 0.97.5, or earlier)
  3. Check if WWPack support is compiled in
    Run 'clamscan --debug 2>&1 | grep -i wwpack' or check the ClamAV compilation options in '/etc/clamav/clamd.conf' for enable support
    Affected if WWPack support is enabled in the ClamAV build - the decompression module vulnerable to heap corruption is active
  4. Verify Debian/Fedora system package version
    On Debian run 'dpkg -l | grep clamav', on Fedora run 'rpm -qa | grep clamav' to check the installed package version
    Affected if Running Debian 8.0, 9.0, or 10.0 with ClamAV packages, or Fedora 17 or 18 with ClamAV packages, that are below version 0.97.7

A system is affected if ClamAV version is below 0.97.7 and the WWPack decompression module is enabled or compiled into the installation.

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.

dbcve · scoped
Upgrade available Upgrade to 0.97.7 or later
Fixed in 0.97.7
Interim mitigation

Upgrade ClamAV to version 0.97.7 or later to remediate the vulnerability. Verify signature database updates continue to function post-upgrade.

Recommended fix High confidence

ClamAV 0.97.7 or later

  1. Update your package repository metadata: 'apt-get update' (Debian) or 'yum check-update' or 'dnf check-update' (Fedora)
  2. Install the updated ClamAV package: 'apt-get install clamav' (Debian) or 'yum update clamav' or 'dnf update clamav' (Fedora)
  3. Restart the clamd service if running: 'service clamd restart' or 'systemctl restart clamd'
  4. Verify the installed version is 0.97.7 or later: 'clamd --version' or 'clamscan --version'

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Debian Linux Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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