How severe is CVE-2001-0060?

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

Is CVE-2001-0060 being actively exploited?

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

What products are affected by CVE-2001-0060?

CVE-2001-0060 primarily affects Stunnel. 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-0060?

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-0060 published?

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

CVE-2001-0060

CVE-2001-0060 is a critical-severity vulnerability in Stunnel 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: 3% (85th percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Stunnel
Published: 2001-02-12
Last modified: 2026-06-16

Description

Format string vulnerability in stunnel 3.8 and earlier allows attackers to execute arbitrary commands via a malformed ident username.

Frequently asked questions

What is CVE-2001-0060?: Format string vulnerability in stunnel 3.8 and earlier allows attackers to execute arbitrary commands via a malformed ident username.
How severe is CVE-2001-0060?: CVE-2001-0060 has a CVSS 2.0 base score of 10.0, rated critical severity.
Is CVE-2001-0060 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 3% (85th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2001-0060?: CVE-2001-0060 primarily affects Stunnel. 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-0060?: 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-0060 published?: CVE-2001-0060 was published on 2001-02-12 and last updated on 2026-06-16.

References

Affected products (4)

cpe:2.3:a:stunnel:stunnel:3.3:*:*:*:*:*:*:*
cpe:2.3:a:stunnel:stunnel:3.4a:*:*:*:*:*:*:*
cpe:2.3:a:stunnel:stunnel:3.7:*:*:*:*:*:*:*
cpe:2.3:a:stunnel:stunnel:3.8:*:*:*:*:*:*:*

More vulnerabilities in Stunnel

CVE-2011-2940 — Critical (CVSS 9.3): stunnel 4.40 and 4.41 might allow remote attackers to execute arbitrary code or cause a denial of service (heap memory…
CVE-2021-20230 — High (CVSS 7.5): A flaw was found in stunnel before 5.57, where it improperly validates client certificates when it is configured to use…
CVE-2002-0002 — High (CVSS 7.5): Format string vulnerability in stunnel before 3.22 when used in client mode for (1) smtp, (2) pop, or (3) nntp allows…
CVE-2008-2400 — High (CVSS 7.2): Unspecified vulnerability in stunnel before 4.23, when running as a service on Windows, allows local users to gain…
CVE-2008-2420 — Medium (CVSS 6.8): The OCSP functionality in stunnel before 4.24 does not properly search certificate revocation lists (CRL), which allows…
CVE-2013-1762 — Medium (CVSS 6.6): stunnel 4.21 through 4.54, when CONNECT protocol negotiation and NTLM authentication are enabled, does not correctly…

All CVEs affecting Stunnel →