CVE-2002-0420
CVE-2002-0420 is a high-severity vulnerability in Claymore Systems Inc Puretls 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% (72nd percentile)
- Actively exploited: Not listed in CISA KEV
- Affected product: Claymore Systems Inc Puretls
- Published:
- Last modified:
Description
Vulnerability in PureTLS before 0.9b2 related to injection attacks, which could possibly allow remote attackers to corrupt or hijack user sessions.
Frequently asked questions
- What is CVE-2002-0420?
- Vulnerability in PureTLS before 0.9b2 related to injection attacks, which could possibly allow remote attackers to corrupt or hijack user sessions.
- How severe is CVE-2002-0420?
- CVE-2002-0420 has a CVSS 2.0 base score of 7.5, rated high severity.
- Is CVE-2002-0420 being actively exploited?
- It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (72nd percentile), an estimate of the probability of exploitation in the next 30 days.
- What products are affected by CVE-2002-0420?
- CVE-2002-0420 affects Claymore Systems Inc Puretls. See the affected-products list for the exact vulnerable versions.
- How do I fix CVE-2002-0420?
- 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-0420 published?
- CVE-2002-0420 was published on 2002-08-12 and last updated on 2026-06-16.
References
- http://archives.neohapsis.com/archives/bugtraq/2002-03/0056.html
- http://www.iss.net/security_center/static/8386.php
- http://www.securityfocus.com/bid/4237
Affected products (1)
- cpe:2.3:a:claymore_systems_inc:puretls:0.9b1:*:*:*:*:*:*:*
More vulnerabilities in Claymore Systems Inc Puretls
- CVE-2005-4839 — Medium (CVSS 5.0): PureTLS before 0.9b5 does not clear optional Extensions and Algorithm.Parameters values before parsing, which might…