CVE-2011-1003
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 · uneditedDouble free vulnerability in the vba_read_project_strings function in vba_extract.c in libclamav in ClamAV before 0.97 might allow remote attackers to execute arbitrary code via crafted Visual Basic for Applications (VBA) data in a Microsoft Office document. NOTE: some of these details are obtained from third party information.
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 · high confidenceA double-free vulnerability exists in the vba_read_project_strings function in vba_extract.c within libclamav versions prior to 0.97. When parsing Visual Basic for Applications (VBA) data embedded in Microsoft Office documents, the function incorrectly frees memory twice, potentially allowing a remote attacker to execute arbitrary code via specially crafted VBA content.
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<= 0.96.5= 0.01= 0.02= 0.3= 0.03= 0.05= 0.8= 0.9= 0.10= 0.12= 0.13= 0.14CVSS 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
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/Au:N/C:P/I:P/A:P
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 checksWork through these to decide whether this CVE applies to you.
-
Check ClamAV versionRun 'clamscan --version' or 'clamd --version' to display the installed ClamAV engine version numberAffected if The displayed version is 0.96.5 or lower, or matches any of these specific versions: 0.01, 0.02, 0.3, 0.03, 0.05, 0.8, 0.9, 0.10, 0.12, 0.13, or 0.14
-
Verify libclamav library versionIf ClamAV is used as a library, check the installed libclamav version via package manager or 'ldd' on the linked binary, then cross-reference with the library file versionAffected if The libclamav library version matches the affected versions listed above
-
Confirm VBA parsing capability is enabledCheck clamd.conf for the presence and value of the 'olevba' directive, or verify that Office document scanning (VBA macro detection) is active in the configurationAffected if VBA parsing (olevba) is enabled and the ClamAV version is within the affected range
You are affected if your installed ClamAV or libclamav version is 0.96.5 or lower (or matches any of the specific affected versions 0.01 through 0.14) and VBA macro scanning is enabled for parsing Microsoft Office documents.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade ClamAV to version 0.97 or later to patch the double-free vulnerability in the VBA parsing code.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-1003 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sources- secunia.com
- www.vupen.com
- www.vupen.com
- git.clamav.net
- git.clamav.net
- lists.fedoraproject.org
- lists.fedoraproject.org
- lists.opensuse.org
- openwall.com
- openwall.com
- osvdb.org
- secunia.com
- secunia.com
- securitytracker.com
- www.mandriva.com
- www.securityfocus.com
- www.ubuntu.com
- www.vupen.com
- exchange.xforce.ibmcloud.com
- wwws.clamav.net
- nvd.nist.gov
Practitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2011-1003 in production — separate from our analysis above.
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.
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.
- 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