How severe is CVE-2001-0111?

CVE-2001-0111 has a CVSS 2.0 base score of 7.2, rated high severity.

Is CVE-2001-0111 being actively exploited?

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

What products are affected by CVE-2001-0111?

CVE-2001-0111 primarily affects Sam Lantinga Splitvt. In total, 7 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2001-0111?

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

When was CVE-2001-0111 published?

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

CVE-2001-0111

CVE-2001-0111 is a high-severity vulnerability in Sam Lantinga Splitvt with a CVSS 2.0 base score of 7.2. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: High (CVSS 2.0 base score 7.2)
EPSS exploit prediction: 1% (66th percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Sam Lantinga Splitvt
Published: 2001-03-12
Last modified: 2026-06-16

Description

Format string vulnerability in splitvt before 1.6.5 allows local users to execute arbitrary commands via the -rcfile command line argument.

Frequently asked questions

What is CVE-2001-0111?: Format string vulnerability in splitvt before 1.6.5 allows local users to execute arbitrary commands via the -rcfile command line argument.
How severe is CVE-2001-0111?: CVE-2001-0111 has a CVSS 2.0 base score of 7.2, rated high severity.
Is CVE-2001-0111 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (66th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2001-0111?: CVE-2001-0111 primarily affects Sam Lantinga Splitvt. In total, 7 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2001-0111?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2001-0111 published?: CVE-2001-0111 was published on 2001-03-12 and last updated on 2026-06-16.

References

Affected products (7)

cpe:2.3:a:sam_lantinga:splitvt:1.6.4:*:*:*:*:*:*:*
cpe:2.3:o:debian:debian_linux:2.2:*:*:*:*:*:*:*
cpe:2.3:o:debian:debian_linux:2.2:*:68k:*:*:*:*:*
cpe:2.3:o:debian:debian_linux:2.2:*:alpha:*:*:*:*:*
cpe:2.3:o:debian:debian_linux:2.2:*:arm:*:*:*:*:*
cpe:2.3:o:debian:debian_linux:2.2:*:powerpc:*:*:*:*:*
cpe:2.3:o:debian:debian_linux:2.2:*:sparc:*:*:*:*:*

More vulnerabilities in Sam Lantinga Splitvt

CVE-2008-0162 — High (CVSS 7.2): misc.c in splitvt 1.6.6 and earlier does not drop group privileges before executing xprop, which allows local users to…
CVE-2001-0112 — High (CVSS 7.2): Multiple buffer overflows in splitvt before 1.6.5 allow local users to execute arbitrary commands.
CVE-2000-0467 — High (CVSS 7.2): Buffer overflow in Linux splitvt 1.6.3 and earlier allows local users to gain root privileges via a long password in…
CVE-1999-0316 — High (CVSS 7.2): Buffer overflow in Linux splitvt command gives root access to local users.

All CVEs affecting Sam Lantinga Splitvt →