Menu

Star on GitHub · 3.2k

CVE-1999-0248

10.0 · HIGH

A race condition in the authentication agent mechanism of sshd 1.2.17 allows an attacker to steal another user's credentials.

Published Jan 1, 1999sshEPSS 1.60%

Overview

CVE-1999-0248 is a high-severity vulnerability affecting ssh ssh. It was published on January 1, 1999 and has a CVSS 2.0 base score of 10.0 (HIGH).

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

Technical description

A race condition in the authentication agent mechanism of sshd 1.2.17 allows an attacker to steal another user's credentials.

Remediation

Check the references section for vendor advisories and patches from ssh. Update ssh 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

Frequently asked questions

What is CVE-1999-0248?

CVE-1999-0248 is a high-severity vulnerability affecting ssh ssh. It was published on January 1, 1999 and has a CVSS 2.0 base score of 10.0 (HIGH).

How severe is CVE-1999-0248?

This vulnerability has a CVSS 2.0 base score of 10.0, 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-0248?

Check the references section for vendor advisories and patches from ssh. Update ssh 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-0248?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-1999-0248 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.