CVE-2007-1281
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 · uneditedKaspersky AntiVirus Engine 6.0.1.411 for Windows and 5.5-10 for Linux allows remote attackers to cause a denial of service (CPU consumption) via a crafted UPX compressed file with a negative offset, which triggers an infinite loop during decompression.
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 confidenceKaspersky AntiVirus Engine versions 6.0.1.411 (Windows) and 5.5-10 (Linux) contain a vulnerability in UPX decompression logic where a crafted UPX compressed file with a negative offset triggers an infinite loop, causing sustained CPU consumption and denial of service.
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= 6.0.1.411= 5.5.10CVSS 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
- Complete
AV:N/AC:L/Au:N/C:N/I:N/A:C
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 Windows Kaspersky AntiVirus engine versionOpen Windows Registry and navigate to HKLM\SOFTWARE\KasperskyLab\ or check the version of kavsvc.exe or avp.exe in the installation directory by running: 'wmic product where "name like 'Kaspersky%'" get version, name' or right-click the executable and view Properties > DetailsAffected if The installed version equals exactly 6.0.1.411
-
Check Linux Kaspersky AntiVirus engine versionRun 'rpm -qa | grep -i kaspersky' or 'dpkg -l | grep -i kaspersky' to list installed Kaspersky packages, then run 'kavscanner -v' or check the version of the kavscanner binary with 'file' or its version flagAffected if The installed version equals exactly 5.5.10 or falls within the 5.5-10 range for Linux versions
-
Verify UPX decompression is enabled in the engineCheck the Kaspersky AntiVirus configuration settings for archive scanning. On Windows, look in the application interface under Settings > Protection > Scan > Archive scanning. On Linux, check /etc/kav/ or the configuration files for archive scanning options that include UPX file decompressionAffected if Archive/UPX decompression scanning is enabled and the engine will parse UPX-packed executables during scans
You are affected if your Kaspersky AntiVirus Engine version is exactly 6.0.1.411 on Windows or 5.5-10 on Linux, and UPX archive decompression scanning is enabled in the configuration.
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 dataUpdate Kaspersky AntiVirus to a version newer than 6.0.1.411 for Windows or 5.5-10 for Linux, as later versions patched the infinite loop vulnerability in the UPX decompression routine.
- Consultation2.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-1281 — 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-2007-1281 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