dbcve.org
Kaspersky Anti VirusApplication · Kaspersky Lab

CVE-2006-1091

HIGH · 7.8 CVSS v2.0 Published 2006-03-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
87/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
Kaspersky Antivirus 5.0.5 and 5.5.3 allows remote attackers to cause a denial of service (CPU and memory consumption) via unknown attack vectors.

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 · low confidence

Kaspersky Antivirus versions 5.0.5 and 5.5.3 contain a denial of service vulnerability allowing remote attackers to cause excessive CPU and memory consumption. The specific attack vectors remain undisclosed in available documentation.

MitigationUpgrade Kaspersky Antivirus to a current supported version beyond 5.x. For legacy systems that cannot be upgraded, implement network segmentation and restrict external access to minimize attack surface.

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
Kaspersky Anti VirusApplication
Affected:= 5.0.5= 5.5.3

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Check if Kaspersky Antivirus is installed
    Open Control Panel > Programs and Features, or run 'wmic product get name,version' to list installed software, or check for Kaspersky processes in Task Manager
    Affected if Kaspersky Antivirus appears in installed programs or running processes
  2. Identify the installed Kaspersky version
    Right-click the Kaspersky icon in the system tray and select 'About', or in Control Panel > Programs and Features click on Kaspersky Antivirus to view version details, or check the application log files typically found in C:\Documents and Settings\All Users\Application Data\Kaspersky Lab\
    Affected if The version displayed is exactly 5.0.5 or exactly 5.5.3
  3. Verify the exact version number
    Locate the executable or DLL version info - typically avp.exe or a similar main executable in the Kaspersky install directory (commonly C:\Program Files\Kaspersky Lab\), right-click and view Properties > Version
    Affected if File version shows 5.0.5.0 or 5.5.3.0 specifically

A system is affected only if Kaspersky Antivirus version 5.0.5 or 5.5.3 is installed and running.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Kaspersky Antivirus to a current supported version beyond 5.x. For legacy systems that cannot be upgraded, implement network segmentation and restrict external access to minimize attack surface.

Fix this in Kaspersky Anti Virus Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2006-1091 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2006-1091 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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