CVE-2006-4265
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 Anti-Hacker 1.8.180, when Stealth Mode is enabled, allows remote attackers to obtain responses to ICMP (1) timestamp and (2) netmask requests, which is inconsistent with the documented behavior of Stealth Mode.
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 Anti-Hacker 1.8.180 with Stealth Mode enabled incorrectly responds to ICMP timestamp and netmask requests, contradicting the documented behavior that Stealth Mode should block all unsolicited inbound traffic. This information disclosure allows remote attackers to confirm the presence of a live host and potentially gather network topology information.
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= 1.8.180CVSS 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
- Partial
- Integrity
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:N/A:N
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-Hacker versionCheck the installed version of Kaspersky Anti-Hacker on the system. This may be found in the program's About or Help section, or via the Windows Add/Remove Programs list, or by examining the program's executable file properties.Affected if The installed version is exactly 1.8.180 (other versions are not affected by this specific CVE).
-
Confirm Stealth Mode is enabledOpen the Kaspersky Anti-Hacker interface and navigate to the Stealth Mode settings. Check whether Stealth Mode is currently turned ON or enabled.Affected if Stealth Mode is enabled (the vulnerability only manifests when Stealth Mode is turned on).
-
Test ICMP timestamp responseFrom a remote system, send an ICMP timestamp request to the protected host using tools such as nmap (-sN flag) or hping3. Observe whether the target responds with timestamp values.Affected if The host responds to ICMP timestamp requests with valid timestamp values (a response indicates vulnerability).
-
Test ICMP netmask responseFrom a remote system, send an ICMP address mask request to the protected host using tools such as nmap (-sM flag) or hping3. Observe whether the target responds with netmask information.Affected if The host responds to ICMP netmask requests with netmask information (a response indicates vulnerability).
A system is affected if it runs Kaspersky Anti-Hacker version 1.8.180 with Stealth Mode enabled AND responds to ICMP timestamp or netmask requests, which contradicts the expected behavior of blocking all unsolicited inbound traffic.
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 dataSince this is a product-level vulnerability in a 2006-era Kaspersky product that is likely End-of-Life, the recommended remediation is to upgrade to a modern Kaspersky security product or replace with an alternative firewall solution that properly blocks ICMP timestamp and netmask requests.
- Consultation1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2006-4265 — 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-2006-4265 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