FedoraOperating system · Fedoraproject
CVE-2014-9328
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 · uneditedClamAV before 0.98.6 allows remote attackers to have unspecified impact via a crafted upack packer file, related to a "heap out of bounds condition."
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 confidenceHeap out-of-bounds condition in ClamAV's upack packer parser before version 0.98.6 allows remote attackers to potentially execute arbitrary code or cause denial of service via a specially crafted upack-packed executable file during antivirus scanning.
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
FedoraOperating system
= 20= 21<= 0.98.5CVSS 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
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/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.
-
Verify ClamAV is installedRun `clamd --version` or `clamscan --version` to display the installed ClamAV version. On Fedora, also try `rpm -q clamav`.Affected if ClamAV is not installed on the system.
-
Check installed ClamAV version against vulnerable rangeCompare the version number from step 1 to the affected range: versions 0.98.5 and earlier on any Linux distribution, or ClamAV version 0.98.5 and earlier.Affected if The installed version is 0.98.5 or earlier, or if the version cannot be determined but is known to be <= 0.98.5.
-
Confirm Fedora version if applicableIf running Fedora, run `cat /etc/fedora-release` to check the release version.Affected if Running Fedora 20 or Fedora 21 with any ClamAV version.
-
Identify if upack-packed files are scannedReview scanning workflows or automated tasks to determine whether the system scans executable files that may be packed with the UPX or similar packers. Check logs or configuration for evidence of upack-related scanning activity.Affected if The system is used to scan untrusted or unknown executable files, particularly those that may have been packed using the upack packer.
You are affected if ClamAV version 0.98.5 or earlier is installed and the system is used to scan upack-packed executable files during antivirus scanning.
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.98.6 or later. As an interim workaround, avoid scanning untrusted or unknown upack-packed files.
Fix this in Fedora
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.0 h
- Testing2.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 $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-9328 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2014-9328 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