Bug 170682

Summary:	CAN-2005-3185 NTLM buffer overflow
Product:	[Fedora] Fedora	Reporter:	Josh Bressers <bressers>
Component:	curl	Assignee:	Ivana Varekova <varekova>
Status:	CLOSED ERRATA	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4	Keywords:	Security
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
URL:	http://article.gmane.org/gmane.comp.web.wget.general/5064
Whiteboard:	reported=20051012,public=20051012,impact=moderate,source=vendorsec
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2005-10-19 14:29:54 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Josh Bressers 2005-10-13 18:06:53 UTC

+++ This bug was initially created as a clone of Bug #170678 +++

This text was scavanged from the libcurl advisory:

libcurl's NTLM function can overflow a stack-based buffer if given a too long
user name or domain name. This would happen if you enable NTLM authentication
and either:

 A - pass in a user name and domain name to libcurl that together are longer
     than 192 bytes

 B - allow (lib)curl to follow HTTP "redirects" (Location: and the appropriate
     HTTP 30x response code) and the new URL contains a URL with a user name
     and domain name that together are longer than 192 bytes

-- Additional comment from bressers on 2005-10-13 13:24 EST --
Created an attachment (id=119931)
Proposed patch from upstream

Comment 1 Josh Bressers 2005-10-13 18:07:42 UTC

This issue also affects FC3

Comment 2 Mark J. Cox 2005-10-14 10:23:34 UTC

On Fedora Core 4 this is not a security issue; curl is compiled using
-D_FORTIFY_SOURCE=2 which catches and blocks this issue.  Therefore on Fedora
Core 4 this can only result in the program being aborted, which is not classed
as a security issue.

Please make a note of this in the advisory of any FC4 update to curl.

Comment 3 Ivana Varekova 2005-10-18 13:53:50 UTC

This bug is fixed in the last fc3 version.