CVE-2007-1880
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 · uneditedInteger overflow in the _NtSetValueKey function in klif.sys in Kaspersky Anti-Virus, Anti-Virus for Workstations, Anti-Virus for File Server 6.0, and Internet Security 6.0 before Maintenance Pack 2 build 6.0.2.614 allows context-dependent attackers to execute arbitrary code via a large, unsigned "data size argument," which results in a heap overflow.
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 confidenceInteger overflow in the _NtSetValueKey function in klif.sys (Kaspersky kernel driver) allows context-dependent attackers to execute arbitrary code via a large unsigned data size argument, causing a heap overflow. The vulnerability affects Kaspersky Anti-Virus, Anti-Virus for Workstations, Anti-Virus for File Server 6.0, and Internet Security 6.0 before Maintenance Pack 2 build 6.0.2.614.
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= 6.0<= 6.0.1.411CVSS 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
- Local
- Complexity
- M
- Authentication
- Single
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:L/AC:M/Au:S/C:C/I:C/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.
-
Verify Kaspersky product is installedCheck for Kaspersky processes or services. Look for processes named 'avp.exe', 'ksafe.exe', or services starting with 'Kaspersky'. On Windows, check Registry key HKLM\SOFTWARE\KasperskyLab for installed products.Affected if No Kaspersky product is installed, the system is not affected.
-
Locate klif.sys driver fileFind klif.sys in the Kaspersky installation directory, typically in C:\Program Files\Kaspersky Lab\*\drivers\ or C:\Windows\System32\drivers\. Use 'dir /s C:\klif.sys' or search the installation folder.Affected if The klif.sys file does not exist, the vulnerability is not present.
-
Check klif.sys file versionRight-click klif.sys, select Properties, then Details. Record the File Version. Alternatively, use: wmic datafile where "name='C:\\Program Files\\Kaspersky Lab\\*\\drivers\\klif.sys'" get VersionAffected if File version is lower than 6.0.2.614 or the version cannot be determined and the product is Kaspersky 6.0 series.
-
Check installed product versionCheck the main Kaspersky product version. Look in Add/Remove Programs for 'Kaspersky Anti-Virus 6.0' or 'Kaspersky Internet Security 6.0', or check Registry under HKLM\SOFTWARE\KasperskyLab\*\Products\ for the version string.Affected if Product version is 6.0.x (any build) or 6.0.1.411 and below, and klif.sys version is below 6.0.2.614.
The system is affected if a Kaspersky 6.0 series product is installed with klif.sys version below 6.0.2.614, as the integer overflow in the _NtSetValueKey function can be triggered.
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 dataApply Kaspersky Anti-Virus/Internet Security 6.0 Maintenance Pack 2 (build 6.0.2.614) or later to patch the klif.sys driver and remediate the integer overflow vulnerability.
- Consultation2.0 h
- Implementation3.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-1880 — 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-1880 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