From ${URL} : It was discovered that the python-requests Proxy-Authorization header was never re-evaluated when a redirect occurs. The Proxy-Authorization header was sent to any new proxy or non-proxy destination as redirected. References: https://github.com/kennethreitz/requests/issues/1885#issuecomment-33793651 Upstream Commit: https://github.com/kennethreitz/requests/commit/4d8cb3244e8e4f84b250c10a48e025f9a8bf6137 @maintainer(s): after the bump, in case we need to stabilize the package, please let us know if it is ready for the stabilization or not.
So this is actually an oldie: http://www.openwall.com/lists/oss-security/2014/09/19/1 Fixed in 2.3.0 already.
So 2.3.0 was already being stabilized in bug 513278. CC'ing the rest of the arches here to bump priority a little bit.
When doing cleanup of old versions, beware of these reverse deps: dev-python/docker-py-0.5.0-r1 ~dev-python/requests-2.2.1 media-video/subliminal-0.6.3 ~dev-python/requests-0.14.2
ppc stable
Please continue with stabilization.
ppc64 stable
x86 stable. Maintainer(s), please cleanup. Security, please vote.
GLSA vote: no.
Arches and Maintainer(s), Thank you for your work. GLSA Vote: No
CVE-2014-1830 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2014-1830): Requests (aka python-requests) before 2.3.0 allows remote servers to obtain sensitive information by reading the Proxy-Authorization header in a redirected request. CVE-2014-1829 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2014-1829): Requests (aka python-requests) before 2.3.0 allows remote servers to obtain a netrc password by reading the Authorization header in a redirected request.
