LiveActive security incident?Get immediate response
CVE Record

CVE-2002-0666: IPSEC implementations including (1) FreeS/WAN and (2) KAME do not properly calculate the length of authenti...

IPSEC implementations including (1) FreeS/WAN and (2) KAME do not properly calculate the length of authentication data, which allows remote attackers to cause a denial of service (kernel panic) via spoofed, short Encapsulating Security Payload (ESP) packets, which result in integer signedness errors.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2002-0666 is a denial-of-service flaw in some older IPsec implementations, including FreeS/WAN and KAME. A remote attacker could send malformed ESP traffic that may crash the kernel, disrupting VPN or encrypted network connectivity. The source data does not identify active exploitation or a specific vendor patch.

Executive priority

Treat as a legacy availability risk. Prioritize if the organization still operates old IPsec VPN infrastructure or exposed ESP services. If no FreeS/WAN, KAME, or derivative stack is present, urgency is lower, but validation should be quick.

Technical view

The issue involves incorrect authentication-data length calculation in IPsec ESP handling. Spoofed, short ESP packets can trigger integer signedness errors, leading to kernel panic in affected FreeS/WAN and KAME implementations. Public source data is sparse and lists no CVSS score, CWE, affected versions, or remediation advisory.

Likely exposure

Exposure is most likely in legacy systems using FreeS/WAN or KAME-derived IPsec stacks, especially internet-reachable VPN gateways or hosts accepting ESP traffic. Modern supported IPsec implementations may not be affected, but the provided sources do not confirm affected version ranges.

Exploitation context

The CVE describes remote denial of service through malformed ESP packets. It is not listed as CISA KEV in the provided bundle, and no cited source confirms active exploitation. Impact is availability-focused: kernel panic and service disruption, not documented data theft or code execution.

Researcher notes

The public record is minimal: no CVSS, CWE, version ranges, exploit status, or patch details are provided. Analysis should focus on confirming affected IPsec lineage and obtaining historical vendor advisories before assigning environment-specific severity.

Mitigation direction

  • Inventory systems using FreeS/WAN, KAME, or KAME-derived IPsec components.
  • Check vendor or operating-system advisories for fixed versions or configuration guidance.
  • Replace unsupported legacy IPsec stacks with maintained alternatives where feasible.
  • Limit ESP exposure to trusted peers using network controls where operationally possible.
  • Monitor VPN and kernel logs for unexpected crashes or malformed IPsec traffic indicators.

Validation and detection

  • Confirm whether any production hosts run FreeS/WAN or KAME IPsec code.
  • Identify internet-facing systems that accept IPsec ESP traffic.
  • Review OS and appliance security advisories for CVE-2002-0666 references.
  • Verify whether affected systems have vendor-supported updates or replacements available.
  • Document compensating controls for systems that cannot be upgraded.
Prepared
Confidence
medium
Sources
2

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2002-0666 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
1Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.