CVE-2005-3912

Description

Format string vulnerability in miniserv.pl Perl web server in Webmin before 1.250 and Usermin before 1.180, with syslog logging enabled, allows remote attackers to cause a denial of service (crash or memory consumption) and possibly execute arbitrary code via format string specifiers in the username parameter to the login form, which is ultimately used in a syslog call. NOTE: the code execution might be associated with an issue in Perl.

7.5

CVSS

Severity: High

CVSS 2.0 •

EPSS 22.75% Top 5%

Vendor Advisory gentoo.org Vendor Advisory debian.org Vendor Advisory novell.com Vendor Advisory mandriva.com Vendor Advisory webmin.com Vendor Advisory webmin.com Vendor Advisory webmin.com

Affected: n/a n/a

References

Link	Tags
http://www.webmin.com/security.html	vendor advisory
http://secunia.com/advisories/17749	third party advisory patch
http://www.gentoo.org/security/en/glsa/glsa-200512-02.xml	third party advisory vendor advisory
http://lists.immunitysec.com/pipermail/dailydave/2005-November/002685.html	patch mailing list third party advisory
http://www.debian.org/security/2006/dsa-1199	third party advisory vendor advisory
http://www.webmin.com/changes-1.250.html	vendor advisory
http://secunia.com/advisories/18101	third party advisory
http://www.vupen.com/english/advisories/2005/2660	third party advisory vdb entry
http://www.novell.com/linux/security/advisories/2005_30_sr.html	third party advisory vendor advisory
http://secunia.com/advisories/17878	third party advisory
http://www.dyadsecurity.com/webmin-0001.html	third party advisory patch
http://www.securityfocus.com/archive/1/418093/100/0/threaded	mailing list third party advisory vdb entry
http://www.webmin.com/uchanges-1.180.html	vendor advisory
http://secunia.com/advisories/22556	third party advisory
http://www.mandriva.com/security/advisories?name=MDKSA-2005:223	third party advisory vendor advisory
http://secunia.com/advisories/17942	third party advisory
http://secunia.com/advisories/17817	third party advisory

Frequently Asked Questions

What is the severity of CVE-2005-3912?: CVE-2005-3912 has been scored as a high severity vulnerability.
How to fix CVE-2005-3912?: To fix CVE-2005-3912, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2005-3912 being actively exploited in the wild?: It is possible that CVE-2005-3912 is being exploited or will be exploited in a near future based on public information. According to its EPSS score, there is a ~23% probability that this vulnerability will be exploited by malicious actors in the next 30 days.