Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <50BE2E85.5060200@redhat.com>
Date: Tue, 04 Dec 2012 10:10:29 -0700
From: Kurt Seifried <kseifried@...hat.com>
To: oss-security@...ts.openwall.com
CC: Jan Lieskovsky <jlieskov@...hat.com>,
        "Steven M. Christey" <coley@...us.mitre.org>,
        "Richard J. Moore" <rich@....org>
Subject: Re: CVE Request -- Qt (x < 4.8.4): QML XmlHttpRequest
 insecure redirection

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 12/04/2012 07:58 AM, Jan Lieskovsky wrote:
> Hello Kurt, Steve, vendors,
> 
> Qt upstream has released 4.8.4 version correcting one security 
> issue:
> 
> An information disclosure flaw was found in the way XMLHttpRequest 
> object implementation in Qt, a software toolkit for developing 
> applications, performed management of certain HTTP responses. 
> Previous implementation allowed redirection from HTTP protocol to
> file schemas. Also the redirection handling was performed 
> automatically by QML application and could not be disabled. A
> remote attacker could use this flaw to cause QML application in an
> unauthorized way to read local file content by causing the HTTP
> response for the application to be a redirect to a file: URL (file
> scheme).
> 
> References: [1]
> http://lists.qt-project.org/pipermail/announce/2012-November/000014.html
>
> 
[2] https://bugzilla.redhat.com/show_bug.cgi?id=883415
> 
> Relevant upstream patch: [3]
> https://codereview.qt-project.org/#change,40034
> 
> Could you allocate a CVE id for this?
> 
> Thank you && Regards, Jan. -- Jan iankko Lieskovsky / Red Hat
> Security Response Team

Please use CVE-2012-5624 for this issue.

- -- 
Kurt Seifried Red Hat Security Response Team (SRT)
PGP: 0x5E267993 A90B F995 7350 148F 66BF 7554 160D 4553 5E26 7993

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBAgAGBQJQvi6FAAoJEBYNRVNeJnmTphkP/AmZ83+7kVystL5+DG5IHfb1
5EOs3bm7csaxAVXaStv7NnU0fP5YpzCUrnYEjDhmB1zMMXla5oyW2+pLI48OnRKP
0JotWmNm6l0bNKpM3P8xeb1nEeJjaXUGgoTX25/+N5+JDnH+qqQ4xlAS2+MlGGiu
uVjU3Neb8TpBMqx8wuNA4qYevuVrhO5rjgEZcFO/BaQXXmPjB76Tdg5GDL4of+i+
CLO6X/4TsTCarZ/cNekwDMKUzVgunD77H27cimpldcWoecmv2MZRFS1hei8w+iPQ
intBhTzG+WzJxzSGgSOkY8eUJi8Hftdi8DuOqF4xebRjq91YxrGY6Wekfn5Lihjn
SY3BeKZbp/FMxLAk/Ru06klmcFfFNyPf2AW2uGBSemAeYNdtKoOip+t25oQwjlxs
LmzXMMEVUQVtbew8S58OKvrFyjLtSP74YBQ35+AN2uqn8a6nA6fe1jpGGRU2EuJy
kVzokQKBeqy6rjZt1vGMOB0NhSxFUvNtR26LAkzwJ3cEecXiSG/73xcC26pm6D8+
ZIXmT2iB9BalXySdXQigb89u6jSSI+pEMPxD2ooXbZCKkVXfu5u2Iysd16OA3SPf
JsZfwmcmmfO6/ohDt2cSu/T8yYmG2Nao3qiyCtjHQ40q20dHOK8nBYFe2ccXV4md
ztDQIrLrw7MR/sckdHxG
=UliW
-----END PGP SIGNATURE-----

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.