CVE-2008-5747
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 · uneditedF-Prot 4.6.8 for GNU/Linux allows remote attackers to bypass anti-virus protection via a crafted ELF program with a "corrupted" header that still allows the program to be executed. NOTE: due to an error in the initial disclosure, F-secure was incorrectly stated as the vendor.
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 confidenceF-Prot 4.6.8 for GNU/Linux contains a vulnerability where crafted ELF executables with corrupted headers can bypass antivirus detection while still executing. The antivirus engine fails to properly parse and scan malformed ELF headers, allowing malicious binaries to evade detection.
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= 4.6.8CVSS 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
- None
- Integrity
- None
- Availability
- Partial
AV:N/AC:L/Au:N/C:N/I:N/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.
-
Confirm F-Prot Antivirus is installedRun 'rpm -qa | grep -i fprot' or 'dpkg -l | grep -i fprot' or check for /opt/f-prot/ directory existence to determine if F-Prot Antivirus is present on the systemAffected if F-Prot is not installed on the system
-
Identify installed F-Prot versionRun 'fpscan --version' or check /opt/f-prot/f-prot.ini for version information, or use 'rpm -qa | grep fprot' / 'dpkg -l' to list the installed package versionAffected if The installed version is exactly 4.6.8
-
Verify ELF file scanning is enabledCheck the F-Prot configuration file (f-prot.ini or fpscan.conf) for scanning settings related to ELF executables, or run 'fpscan --help' to review available scan options for executable filesAffected if ELF scanning is enabled and the version is 4.6.8
-
Confirm real-time or on-access scanning is activeCheck if the F-Prot daemon (fpscand) is running via 'ps aux | grep fprot' or review configuration for on-access scanning settingsAffected if Real-time scanning is enabled and the version is 4.6.8
The environment is affected if F-Prot Antivirus version 4.6.8 is installed with ELF executable scanning enabled, as malformed ELF headers can evade detection in this specific version.
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 F-Prot Antivirus for Linux to a version newer than 4.6.8, as this vulnerability was addressed in later versions of the product.
- Consultation1.0 h
- Implementation1.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,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2008-5747 — 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-2008-5747 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