Menu

Star on GitHub · 3.2k

CVE-2001-0219

2.1 · LOW

Vulnerability in Support Tools Manager (xstm,cstm,stm) in HP-UX 11.11 and earlier allows local users to cause a denial of service.

Published Mar 26, 2001hpEPSS 0.49%

Overview

CVE-2001-0219 is a low-severity vulnerability affecting hp hp-ux. It was published on March 26, 2001 and has a CVSS 2.0 base score of 2.1 (LOW).

This vulnerability has a CVSS 2.0 base score of 2.1, rated LOW. It requires local or adjacent network access to exploit. No authentication or special privileges are required for exploitation.

Technical description

Vulnerability in Support Tools Manager (xstm,cstm,stm) in HP-UX 11.11 and earlier allows local users to cause a denial of service.

Remediation

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

Frequently asked questions

What is CVE-2001-0219?

CVE-2001-0219 is a low-severity vulnerability affecting hp hp-ux. It was published on March 26, 2001 and has a CVSS 2.0 base score of 2.1 (LOW).

How severe is CVE-2001-0219?

This vulnerability has a CVSS 2.0 base score of 2.1, rated LOW. It requires local or adjacent network access to exploit. No authentication or special privileges are required for exploitation.

How do I fix or remediate CVE-2001-0219?

Check the references section for vendor advisories and patches from hp. Update hp-ux 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-2001-0219?

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

Related LOW CVEs from 2001

View all