Menu

Star on GitHub · 3.2k

CVE-1999-0408

10.0 · HIGH

Files created from interactive shell sessions in Cobalt RaQ microservers (e.g.

Published Feb 25, 1999sunEPSS 1.51%

Overview

CVE-1999-0408 is a high-severity vulnerability affecting sun cobalt_raq. It was published on February 25, 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

Files created from interactive shell sessions in Cobalt RaQ microservers (e.g. .bash_history) are world readable, and thus are accessible from the web server.

Remediation

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

CVE-1999-0408 is a high-severity vulnerability affecting sun cobalt_raq. It was published on February 25, 1999 and has a CVSS 2.0 base score of 10.0 (HIGH).

How severe is CVE-1999-0408?

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-0408?

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

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