[UNIX] Remote Vulnerabilties in mod_ntlm
From: email@example.com To: firstname.lastname@example.org Date: 21 Apr 2003 21:00:38 +0200
The following security advisory is sent to the securiteam mailing list, and can be found at the SecuriTeam web site: http://www.securiteam.com
- - promotion
In the US?
Contact Beyond Security at our new California office
housewarming rates on automated network vulnerability
scanning. We also welcome ISPs and other resellers!
Please contact us at: 323-882-8286 or email@example.com
- - - - - - - - -
Remote Vulnerabilties in mod_ntlm
<http://www.sourceforge.net/projects/modntlm> mod_ntlm is an Apache
module (originally designed for Apache 1.3, now available for Apache 2.0)
that provides the ability for Apache services to authenticate users via
the NTLM authentication technology that is largely specific to Microsoft
The module has been found to contain a pair of remotely exploitable
vulnerabilities that would allow attacker to cause the server to execute
* Apache 1.3: mod_ntlm v0.4 and prior
* Apache 2.0: mod_ntlmv2 v0.1
mod_ntlm contains a pair of remotely exploitable vulnerabilities in its
data logging routine. The vulnerabilities occur in a default build. The
mod_ntlm "log()" function contains a pair of exploitable error conditions:
log(const request_rec * r, const char *format,...)
if ((s = (char *) malloc(2048)) == NULL)
vsprintf(s, format, ap);
ap_log_rerror(APLOG_MARK, APLOG_NOERRNO | APLOG_NOTICE, r, s);
The function is called with user-supplied input in various locations in
the code. The first vulnerability is a heap overflow -- if any
user-supplied input is greater than 2048 characters, memory management
structures are overwritten, and arbitrary code execution is possible.
Secondly, an incorrect call to ap_log_rerror(). The last parameter to
ap_log_rerror() is not a log line, but a format string. Due to the
previous decoding operation, it becomes possible to pass format specifiers
to ap_log_rerror(). A carefully crafted format string may allow code
Either of the following two sessions will cause httpd to exit due to
GET / HTTP/1.0
GET / HTTP/1.0
Similarly, a proxy server can be exploited by using an external URL
(http://www.yahoo.com/, for instance), in place of "/", and using
Proxy-Authorization, in place of Authorization in the examples above.
The vulnerability was submitted to the vendor via SourceForge at:
The vendor has not responded to the bug report as of the time of writing
of this advisory.
The information has been provided by <mailto:firstname.lastname@example.org>
This bulletin is sent to members of the SecuriTeam mailing list.
To unsubscribe from the list, send mail with an empty subject line and body to: email@example.com
In order to subscribe to the mailing list, simply forward this email to: firstname.lastname@example.org
The information in this bulletin is provided "AS IS" without warranty of any kind.
In no event shall we be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages.