CVE-2007-1879
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 StartUploading function in KL.SysInfo ActiveX control (AxKLSysInfo.dll) in Kaspersky Anti-Virus 6.0 and Internet Security 6.0 before Maintenance Pack 2 build 6.0.2.614 allows remote attackers to read arbitrary files by triggering an outbound anonymous FTP session that invokes the PUT command. NOTE: this issue might be related to CVE-2007-1112.
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 confidenceThe KL.SysInfo ActiveX control (AxKLSysInfo.dll) in Kaspersky Anti-Virus 6.0 and Internet Security 6.0 contains a vulnerability in the StartUploading function that allows remote attackers to read arbitrary files by triggering an outbound anonymous FTP session that invokes the PUT command. This is a file disclosure vulnerability in a privileged security product with CVSS 9.3, indicating critical severity.
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.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
- Network
- Complexity
- M
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:M/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.
-
Verify Kaspersky Anti-Virus or Internet Security 6.0 is installedCheck the Windows registry under HKLM\SOFTWARE\KasperskyLab for installed Kaspersky products, or inspect Program Files for Kaspersky Lab foldersAffected if Kaspersky Anti-Virus 6.0 or Internet Security 6.0 is present on the system
-
Determine the exact installed versionOpen Add/Remove Programs or check the About dialog within the Kaspersky application to read the full version and build numberAffected if The version is 6.0 (any build) or 6.0.1.411 or earlier (vulnerable to CVE-2007-1879)
-
Locate the vulnerable ActiveX control DLLSearch for AxKLSysInfo.dll in the Kaspersky installation directory (typically C:\Program Files\Kaspersky Lab\) or subdirectoriesAffected if The file AxKLSysInfo.dll exists on the system, indicating the vulnerable component is present
-
Check if the ActiveX control is registeredQuery the Windows registry under HKCR\CLSID for the CLSID associated with KL.SysInfo (search for 'SysInfo' or the specific CLSID GUID), or use regsvr32 to check registration statusAffected if The ActiveX control is registered and can be instantiated by Internet Explorer
-
Verify outbound FTP capability is not blockedCheck firewall rules or perimeter controls to determine if outbound anonymous FTP connections are allowed from this hostAffected if Outbound anonymous FTP is permitted, which is required for the exploit to function
The system is affected if it runs Kaspersky Anti-Virus or Internet Security version 6.0 through 6.0.1.411 and has the AxKLSysInfo.dll ActiveX control present and registered, allowing a remote attacker to trigger an anonymous FTP PUT command to exfiltrate files.
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.
dbcve · scopedUpgrade Kaspersky Anti-Virus or Internet Security 6.0 to Maintenance Pack 2 build 6.0.2.614 or later. As a compensating control, disable the vulnerable ActiveX control or block outbound anonymous FTP connections at the perimeter.
Kaspersky Anti-Virus 6.0 and Internet Security 6.0 with Maintenance Pack 2 build 6.0.2.614
- Download Maintenance Pack 2 (build 6.0.2.614) for Kaspersky Anti-Virus 6.0 or Internet Security 6.0 from the official Kaspersky support website
- Ensure the system meets the minimum requirements for the update
- Close all running applications and disable real-time protection temporarily
- Run the downloaded installer and follow the on-screen prompts to apply the patch
- Restart the computer after installation completes
- Verify the installed version matches build 6.0.2.614 or higher
- Re-enable real-time protection and ensure antivirus definitions are updated
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.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,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-1879 — 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-1879 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