How severe is CVE-2001-0825?

CVE-2001-0825 has a CVSS 2.0 base score of 10.0, rated critical severity.

Is CVE-2001-0825 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 4% (88th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2001-0825?

CVE-2001-0825 primarily affects Xinetd. In total, 4 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2001-0825?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.

When was CVE-2001-0825 published?

CVE-2001-0825 was published on 2001-12-06 and last updated on 2026-06-16.

CVE-2001-0825

CVE-2001-0825 is a critical-severity vulnerability in Xinetd with a CVSS 2.0 base score of 10.0. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: Critical (CVSS 2.0 base score 10.0)
EPSS exploit prediction: 4% (88th percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Xinetd
Published: 2001-12-06
Last modified: 2026-06-16

Description

Buffer overflow in internal string handling routines of xinetd before 2.1.8.8 allows remote attackers to execute arbitrary commands via a length argument of zero or less, which disables the length check.

Frequently asked questions

What is CVE-2001-0825?: Buffer overflow in internal string handling routines of xinetd before 2.1.8.8 allows remote attackers to execute arbitrary commands via a length argument of zero or less, which disables the length check.
How severe is CVE-2001-0825?: CVE-2001-0825 has a CVSS 2.0 base score of 10.0, rated critical severity.
Is CVE-2001-0825 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 4% (88th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2001-0825?: CVE-2001-0825 primarily affects Xinetd. In total, 4 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2001-0825?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
When was CVE-2001-0825 published?: CVE-2001-0825 was published on 2001-12-06 and last updated on 2026-06-16.

References

Affected products (4)

cpe:2.3:a:xinetd:xinetd:*:*:*:*:*:*:*:*
cpe:2.3:a:xinetd:xinetd:2.1.8.8:*:*:*:*:*:*:*
cpe:2.3:a:xinetd:xinetd:2.1.8.9:*:*:*:*:*:*:*
cpe:2.3:a:xinetd:xinetd:2.3.0:*:*:*:*:*:*:*

More vulnerabilities in Xinetd

CVE-2013-4342 — High (CVSS 7.6): xinetd does not enforce the user and group configuration directives for TCPMUX services, which causes these services to…
CVE-2001-1389 — High (CVSS 7.5): Multiple vulnerabilities in xinetd 2.3.0 and earlier, and additional variants until 2.3.3, may allow remote attackers…
CVE-2000-0536 — High (CVSS 7.5): xinetd 2.1.8.x does not properly restrict connections if hostnames are used for access control and the connecting host…
CVE-2003-0211 — Medium (CVSS 5.0): Memory leak in xinetd 2.3.10 allows remote attackers to cause a denial of service (memory consumption) via a large…
CVE-2012-0862 — Medium (CVSS 4.3): builtins.c in Xinetd before 2.3.15 does not check the service type when the tcpmux-server service is enabled, which…
CVE-2001-1322 — Low (CVSS 3.6): xinetd 2.1.8 and earlier runs with a default umask of 0, which could allow local users to read or modify files that are…

All CVEs affecting Xinetd →