Menu

Star on GitHub · 3.2k

CVE-1999-0428

7.5 · HIGH

OpenSSL and SSLeay allow remote attackers to reuse SSL sessions and bypass access controls.

Published Mar 22, 1999opensslCWE-384EPSS 3.23%

Overview

CVE-1999-0428 is a high-severity vulnerability affecting openssl openssl. It was published on March 22, 1999 and has a CVSS 2.0 base score of 7.5 (HIGH).

This vulnerability has a CVSS 2.0 base score of 7.5, rated HIGH. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

Technical description

OpenSSL and SSLeay allow remote attackers to reuse SSL sessions and bypass access controls.

Remediation

Check the references section for vendor advisories and patches from openssl. Update openssl to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Affected products

VendorProductVersionsStatus
opensslopenssl>= 0, < 0.9.2bAffected

Frequently asked questions

What is CVE-1999-0428?

CVE-1999-0428 is a high-severity vulnerability affecting openssl openssl. It was published on March 22, 1999 and has a CVSS 2.0 base score of 7.5 (HIGH).

How severe is CVE-1999-0428?

This vulnerability has a CVSS 2.0 base score of 7.5, rated HIGH. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

How do I fix or remediate CVE-1999-0428?

Check the references section for vendor advisories and patches from openssl. Update openssl to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-1999-0428?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-1999-0428 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.