How severe is CVE-2005-0385?

CVE-2005-0385 has a CVSS 2.0 base score of 7.2, rated high severity.

Is CVE-2005-0385 being actively exploited?

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

What products are affected by CVE-2005-0385?

CVE-2005-0385 primarily affects Frank Mcingvale Luxman. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2005-0385?

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-2005-0385 published?

CVE-2005-0385 was published on 2005-05-02 and last updated on 2026-06-16.

CVE-2005-0385

CVE-2005-0385 is a high-severity vulnerability in Frank Mcingvale Luxman 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% (69th percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Frank Mcingvale Luxman
Published: 2005-05-02
Last modified: 2026-06-16

Description

Buffer overflow in luxman before 0.41, if used with certain insecure svgalib libraries, allows local users to execute arbitrary code via a long -f command line argument.

Frequently asked questions

What is CVE-2005-0385?: Buffer overflow in luxman before 0.41, if used with certain insecure svgalib libraries, allows local users to execute arbitrary code via a long -f command line argument.
How severe is CVE-2005-0385?: CVE-2005-0385 has a CVSS 2.0 base score of 7.2, rated high severity.
Is CVE-2005-0385 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (69th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2005-0385?: CVE-2005-0385 primarily affects Frank Mcingvale Luxman. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2005-0385?: 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-2005-0385 published?: CVE-2005-0385 was published on 2005-05-02 and last updated on 2026-06-16.

References

Affected products (2)

cpe:2.3:a:frank_mcingvale:luxman:0.41:*:*:*:*:*:*:*
cpe:2.3:a:frank_mcingvale:luxman:0.41_17:*:*:*:*:*:*:*

More vulnerabilities in Frank Mcingvale Luxman

CVE-2002-1245 — High (CVSS 7.2): Maped in LuxMan 0.41 uses the user-provided search path to find and execute the gzip program, which allows local users…

All CVEs affecting Frank Mcingvale Luxman →