How severe is CVE-2002-0872?

CVE-2002-0872 has a CVSS 2.0 base score of 7.5, rated high severity.

Is CVE-2002-0872 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (73rd percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2002-0872?

CVE-2002-0872 primarily affects L2tpd. In total, 6 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2002-0872?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

When was CVE-2002-0872 published?

CVE-2002-0872 was published on 2002-09-05 and last updated on 2026-06-16.

CVE-2002-0872

CVE-2002-0872 is a high-severity vulnerability in L2tpd with a CVSS 2.0 base score of 7.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: High (CVSS 2.0 base score 7.5)
EPSS exploit prediction: 2% (73rd percentile)
Actively exploited: Not listed in CISA KEV
Affected product: L2tpd
Published: 2002-09-05
Last modified: 2026-06-16

Description

l2tpd 0.67 does not initialize the random number generator, which allows remote attackers to hijack sessions.

Frequently asked questions

What is CVE-2002-0872?: l2tpd 0.67 does not initialize the random number generator, which allows remote attackers to hijack sessions.
How severe is CVE-2002-0872?: CVE-2002-0872 has a CVSS 2.0 base score of 7.5, rated high severity.
Is CVE-2002-0872 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (73rd percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2002-0872?: CVE-2002-0872 primarily affects L2tpd. In total, 6 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2002-0872?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2002-0872 published?: CVE-2002-0872 was published on 2002-09-05 and last updated on 2026-06-16.

References

Affected products (6)

cpe:2.3:a:l2tpd:l2tpd:0.62:*:*:*:*:*:*:*
cpe:2.3:a:l2tpd:l2tpd:0.63:*:*:*:*:*:*:*
cpe:2.3:a:l2tpd:l2tpd:0.64:*:*:*:*:*:*:*
cpe:2.3:a:l2tpd:l2tpd:0.65:*:*:*:*:*:*:*
cpe:2.3:a:l2tpd:l2tpd:0.66:*:*:*:*:*:*:*
cpe:2.3:a:l2tpd:l2tpd:0.67:*:*:*:*:*:*:*

More vulnerabilities in L2tpd

CVE-2004-0649 — Critical (CVSS 10.0): Buffer overflow in write_packet in control.c for l2tpd may allow remote attackers to execute arbitrary code.
CVE-2002-0873 — Medium (CVSS 5.0): Vulnerability in l2tpd 0.67 allows remote attackers to overwrite the vendor field via a long value in an…

All CVEs affecting L2tpd →