CVE-2005-1905
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 · uneditedThe klif.sys driver in Kaspersky Labs Anti-Virus 5.0.227, 5.0.228, and 5.0.335 on Windows 2000 allows local users to gain privileges by modifying certain critical code addresses that are later accessed by privileged programs.
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 confidenceThe klif.sys kernel-mode driver in Kaspersky Anti-Virus 5.0.227, 5.0.228, and 5.0.335 on Windows 2000 contains a privilege escalation vulnerability. Local users can modify certain critical code addresses stored in memory that are subsequently accessed and executed by the privileged driver, allowing unprivileged users to gain elevated (system/kernel) privileges.
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= 5.0.227= 5.0.228= 5.0.335= 5.0.227= 5.0.228= 5.0.325CVSS 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
- Low
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:L/AC:L/Au:N/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.
-
Check if Kaspersky Anti-Virus is installedLook for Kaspersky installation directory in Program Files or check registry under HKLM\SOFTWARE\KasperskyLab for installed productsAffected if No Kaspersky product is found - not affected; if found, proceed to version check
-
Identify the installed Kaspersky Anti-Virus versionCheck the product version in the installed program's properties, about dialog, or registry keys under the Kaspersky installation path. Compare against affected versions: 5.0.227, 5.0.228, 5.0.335 (or 5.0.325 for Personal)Affected if Installed version matches exactly 5.0.227, 5.0.228, 5.0.335, or 5.0.325 - likely affected
-
Verify the klif.sys driver presenceCheck for the existence of klif.sys in the Windows\system32\drivers directory or within the Kaspersky installation folderAffected if Driver file exists and version check from step 2 shows affected version - affected
-
Confirm Windows 2000 operating systemRun 'winver' or check system properties to identify the Windows versionAffected if Operating system is Windows 2000 and Kaspersky version matches affected list - vulnerable configuration present
User is affected if Kaspersky Anti-Virus versions 5.0.227, 5.0.228, 5.0.335, or 5.0.325 is installed on Windows 2000 with the klif.sys driver present.
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 Kaspersky Anti-Virus to a current supported version. This vulnerability affects extremely old versions (2005-era) on an end-of-life operating system (Windows 2000), so legacy system migration is the primary remediation.
- 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-2005-1905 — 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-2005-1905 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