Menu

Star on GitHub · 3.2k

CVE-2000-0455

2.1 · LOW

Buffer overflow in xlockmore xlock program version 4.16 and earlier allows local users to read sensitive data from memory via a long -mode option.

Published May 29, 2000david_bagleyEPSS 0.40%

Overview

CVE-2000-0455 is a low-severity vulnerability affecting david_bagley xlock. It was published on May 29, 2000 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

Buffer overflow in xlockmore xlock program version 4.16 and earlier allows local users to read sensitive data from memory via a long -mode option.

Remediation

Check the references section for vendor advisories and patches from david_bagley. Update xlock 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-2000-0455?

CVE-2000-0455 is a low-severity vulnerability affecting david_bagley xlock. It was published on May 29, 2000 and has a CVSS 2.0 base score of 2.1 (LOW).

How severe is CVE-2000-0455?

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-2000-0455?

Check the references section for vendor advisories and patches from david_bagley. Update xlock 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-2000-0455?

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

View all