Skip to content
Fencer Intel
medium 5.0

CVE-2015-2221 json

ClamAV before 0.98.7 allows remote attackers to cause a denial of service (infinite loop) via a crafted y0da cryptor file.

published 11y ago modified 4mo ago also EUVD-2015-2328

cvss
5.0
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
3.2%
EPSS 3.2% chance of exploitation in 30 days, percentile 88%
public exploits
0
none known

Summary

ClamAV before 0.98.7 allows remote attackers to cause a denial of service (infinite loop) via a crafted y0da cryptor file.

Patch / fix

  • clamav Debian 14, Debian 13, Debian 12 0.98.7+dfsg-1

debian advisories DEBIAN-CVE-2015-2221

  • clamav Ubuntu 14.04 LTS 0.98.7+dfsg-0ubuntu0.14.04.1

ubuntu advisories UBUNTU-CVE-2015-2221

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • clamav SLES 12, SLED 12, SLES for SAP 12 0.98.7-13.1

suse advisories SUSE-SU-2015:0882-1SUSE-SU-2015:0882-2

  • clamav openSUSE Tumbleweed 0.99.2-4.1

opensuse advisories openSUSE-SU-2024:10571-1

Is CVE-2015-2221 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2015-2221 updated cvss 4.3

: clamav Infinite loop condition on crafted y0da cryptor file

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

3.19% chance of exploitation in the next 30 days, higher than 88% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:N/I:N/A:P

Classification

Weakness
  • CWE-399 Resource Management Errors

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.