|
Message-ID: <4CB5B87D.2020001@redhat.com> Date: Wed, 13 Oct 2010 15:47:41 +0200 From: Jan Lieskovsky <jlieskov@...hat.com> To: "Steven M. Christey" <coley@...us.mitre.org> CC: oss-security <oss-security@...ts.openwall.com>, Daniel Stenberg <daniel@...x.se> Subject: CVE Request -- cURL / mingw32-cURL -- Did not strip directory parts separated by backslashes, when downloading files Hello Steve, vendors, cURL upstream has released new curl / libcurl v7.21.2 addressing one security flaw, specific for operating systems, where backslashes are used to separate directories from file names. More details follow: cURL did not properly cut off directory parts from user provided file name to be downloaded on operating systems, where backslashes are used to separate directories and file names. This could allow remote servers to create or overwrite files via a Content-Disposition header that suggests a crafted filename, and possibly execute arbitrary code as a consequence of writing to a certain file in a user's home directory. Different vulnerability than CVE-2010-2251, CVE-2010-2252 and CVE-2010-2253. Note: As already mentioned in [2]. This flaw only affected those operating systems, where backslash is used to separate directories and file names, thus Microsoft Windows, Novell Netware, MSDOS, OS/2 and Symbian to mention some of them. References: [1] http://curl.haxx.se/docs/security.html [2] http://curl.haxx.se/docs/adv_20101013.html Upstream patch: [3] http://curl.haxx.se/curl-content-disposition.patch Credit: Upstream acknowledges Dan Fandrich as the original reporter. Red Hat Bugzilla tracking system record: [4] https://bugzilla.redhat.com/show_bug.cgi?id=642642 Could you please allocate a CVE id for this issue? Thanks && Regards, Jan. -- Jan iankko Lieskovsky / Red Hat Security Response Team
Powered by blists - more mailing lists
Please check out the Open Source Software Security Wiki, which is counterpart to this mailing list.
Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.