Skip to content
Noroxi
CVE-2019-1789· NVD / CVE Program· CNA cisco

ClamAV Denial of Service Vulnerability

ClamAV versions prior to 0.101.2 are susceptible to a denial of service (DoS) vulnerability. An out-of-bounds heap read condition may occur when scanning PE files. An example is Windows EXE and DLL files that have been packed using Aspack as a result of inadequate bound-checking.

HighCVSS 7.5 · v3.1—No exploit Fix available
Published
Nov 5, 2019
Updated
Jun 16, 2026
EPSS
1.5% · 73th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

30

Monitor

Low priority for now.

CVSS
30 / 40 · 7.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 1.5%

CISA SSVC decision

Exploitation
none
Automatable
yes
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
7.5
CNA · cisco
7.5
agree

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Affected systems

VendorProduct
clamavclamav

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • clamav clamavbefore 0.101.2

Versions reported by the vendor

Affected version ranges reported by the assigning authority (cisco). Independent of NVD's CPE analysis and usually ahead of it.

  • Cisco ClamAV

    • unspecified and later · before 0.100.3affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Alpine:v3.10clamavbefore 0.100.3-r00.100.3-r0
Debian:12clamavbefore 0.101.2+dfsg-10.101.2+dfsg-1
Debian:8clamavbefore 0.100.3+dfsg-0+deb8u10.100.3+dfsg-0+deb8u1
openSUSE:Leap 15.0clamavbefore 0.100.3-lp150.2.10.10.100.3-lp150.2.10.1
openSUSE:Leap 15.1clamavbefore 0.103.0-lp151.2.12.10.103.0-lp151.2.12.1
openSUSE:Leap 15.2clamavbefore 0.103.0-lp152.6.3.10.103.0-lp152.6.3.1
SUSE:Linux Enterprise Module for Basesystem 15clamavbefore 0.100.3-3.9.10.100.3-3.9.1
SUSE:Linux Enterprise Module for Basesystem 15 SP1clamavbefore 0.103.0-3.23.10.103.0-3.23.1
SUSE:Linux Enterprise Point of Sale 11 SP3clamavbefore 0.100.3-0.20.21.10.100.3-0.20.21.1
SUSE:OpenStack Cloud 7clamavbefore 0.100.3-33.21.10.100.3-33.21.1

Other highest-scoring records for the same primary product.

  • CVE-2023-20032On Feb 15, 2023, the following vulnerability in the ClamAV scanning library was disclosed: A vulnerability in the HFS+ partition file p
    48Plan
  • CVE-2024-20328ClamAV VirusEvent File Processing Command Injection Vulnerability
    46Plan
  • CVE-2017-12379ClamAV AntiVirus software versions 0.99.2 and prior contain a vulnerability that could allow an unauthenticated, remote attacker to cause a
    43Plan
  • CVE-2006-1615Multiple format string vulnerabilities in the logging code in Clam AntiVirus (ClamAV) before 0.88.1 might allow remote attackers to execute
    43Plan
  • CVE-2017-12377ClamAV AntiVirus software versions 0.99.2 and prior contain a vulnerability that could allow an unauthenticated, remote attacker to cause a
    42Plan
  • CVE-2009-1372Stack-based buffer overflow in the cli_url_canon function in libclamav/phishcheck.c in ClamAV before 0.95.1 allows remote attackers to cause
    42Plan

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
alpine:clamav0.100.3-r0 · Alpine:v3.10Package registry (OSV)
debian:clamav0.101.2+dfsg-1 · Debian:12Package registry (OSV)
opensuse:clamav0.100.3-lp150.2.10.1 · openSUSE:Leap 15.0Package registry (OSV)
suse:clamav0.100.3-3.9.1 · SUSE:Linux Enterprise Module for Basesystem 15Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

nvd-primary

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records