ClamavApplication

CVE-2010-4261

HIGH · 7.5 CVSS v2.0 Published 2010-12-07

Fix available

A fix is available. Upgrade to after 0.96.4 or later.

See remediation →

84/100

Remediation priority · High

Remotely reachable No privileges Zero-click

Official description

NVD · unedited

Off-by-one error in the icon_cb function in pe_icons.c in libclamav in ClamAV before 0.96.5 allows remote attackers to cause a denial of service (memory corruption and application crash) or possibly execute arbitrary code via unspecified vectors. NOTE: some of these details are obtained from third party information.

Technical summary

dbcve analysis · high confidence

An off-by-one error exists in the icon_cb function in pe_icons.c within libclamav, affecting ClamAV versions prior to 0.96.5. This memory corruption vulnerability in the PE icon parsing logic can be triggered remotely, potentially allowing attackers to crash the application or execute arbitrary code through specially crafted PE files with malformed icon data.

MitigationUpgrade ClamAV to version 0.96.5 or later to patch the vulnerability. If immediate patching is not possible, consider restricting or disabling the scanning of untrusted PE files until the update can be applied.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

NVD · CPE data

ClamavApplication

Affected:<= 0.96.4= 0.01= 0.02= 0.3= 0.03= 0.05= 0.8= 0.9= 0.10= 0.12= 0.13= 0.14

CVSS breakdown

From the vector

Attack vector: Network
Complexity: Low
Authentication: None
Confidentiality: Partial
Integrity: Partial
Availability: Partial

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

Am I affected?

dbcve checks

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

Check if ClamAV is installed

Run 'clamd --version' or 'clamscan --version' to confirm ClamAV is present on the system

Affected if ClamAV is not installed, then the vulnerability does not apply to this system
Determine installed ClamAV version

Execute 'clamd --version' or 'clamscan --version' and note the version number displayed (e.g., 0.96.4, 0.96.3, etc.)

Affected if The version is less than 0.96.5 (any version from 0.01 through 0.96.4 or listed affected versions) - compare your version to the vulnerable range
Verify libclamav PE scanning is enabled

Check clamd.conf or clamscan configuration for the presence of the 'DetectPUA' option or PE parsing-related settings; PE icon parsing occurs during PE file scanning which is enabled by default in ClamAV

Affected if PE scanning is disabled (not typical default), though the vulnerability still exists in the library code even if not actively invoked
Confirm the vulnerable pe_icons.c component exists

Locate libclamav library file (typically /usr/lib/libclamav.so or similar path) and verify the pe_icons.c compiled code is present within the installed ClamAV version

Affected if The library contains the icon_cb function from pe_icons.c and the version is < 0.96.5

The system is affected if ClamAV is installed with a version lower than 0.96.5 and the PE scanning module (containing the vulnerable icon_cb function in libclamav) is present and operational.

Generated from the published advisory. Verify against your own configuration.

Remediation

From vendor data

Upgrade available Upgrade to a release after 0.96.4

Interim mitigation

Upgrade ClamAV to version 0.96.5 or later to patch the vulnerability. If immediate patching is not possible, consider restricting or disabling the scanning of untrusted PE files until the update can be applied.

Fix this in Clamav Scoped from the published advisory

Consultation2.0 h
Implementation2.0 h
Testing2.0 h
Review / QA1.0 h

7.0 hours of engineering $1,240

Get the upgrade done

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2010-4261 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2010-4261?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

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

At a glance

A fix existsUpgrade to after 0.96.4 or later

Severity 7.5 High

Exploit likelihood EPSS, next 30 days 4.8%

Affects: Clamav

Remediation

A high-priority fix

Fix this in Clamav 7 hrs · Low

Typical engagement from $1,240

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2010-4261 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References