CWE
20 93 113
Advisory Published
CVE Published
Updated

CVE-2016-5699: Input Validation

First published: Mon Nov 24 2014(Updated: )

A vulnerability in Python's http, ftp and url libraries was reported, allowing to inject additional HTTP headers and more. * Upstream bug: <a href="https://bugs.python.org/issue22928">https://bugs.python.org/issue22928</a> * Upstream patches Python 3.4 / 3.5 : revision 94952 : <a href="https://hg.python.org/cpython/rev/bf3e1c9b80e9">https://hg.python.org/cpython/rev/bf3e1c9b80e9</a> Python 2.7 : revision 94951 : <a href="https://hg.python.org/cpython/rev/1c45047c5102">https://hg.python.org/cpython/rev/1c45047c5102</a> Additional note : When used in combination with flaw described in <a class="bz_bug_link bz_status_CLOSED bz_closed bz_public " title="CLOSED ERRATA - CVE-2016-10739 glibc: getaddrinfo should reject IP addresses with trailing characters" href="show_bug.cgi?id=1347549">BZ 1347549</a>, an attacker could direct an HTTP connection to a malicious server, using the following combined issues: * Python's httplib does not validate HTTP header values. A malicious 'Host' header with quoted new lines can inject additional headers and more * glibc's getaddrinfo() ignores new lines and everything after a new line character when the first part looks like a IPv4 address See the following blog post for additional information: <a href="http://blog.blindspotsecurity.com/2016/06/advisory-http-header-injection-in.html">http://blog.blindspotsecurity.com/2016/06/advisory-http-header-injection-in.html</a>

Credit: secalert@redhat.com

Affected SoftwareAffected VersionHow to fix
redhat/python<0:2.6.6-66.el6_8
0:2.6.6-66.el6_8
redhat/python<0:2.7.5-38.el7_2
0:2.7.5-38.el7_2
redhat/python27-python<0:2.7.8-18.el6
0:2.7.8-18.el6
redhat/python33-python<0:3.3.2-18.el6
0:3.3.2-18.el6
redhat/rh-python34-python<0:3.4.2-14.el6
0:3.4.2-14.el6
redhat/rh-python35-python<0:3.5.1-9.el7
0:3.5.1-9.el7
redhat/python27-python<0:2.7.8-16.el7
0:2.7.8-16.el7
redhat/python33-python<0:3.3.2-16.el7
0:3.3.2-16.el7
redhat/rh-python34-python<0:3.4.2-13.el7
0:3.4.2-13.el7
Python 2.7<=2.7.9
Python 2.7=3.0
Python 2.7=3.0.1
Python 2.7=3.1.0
Python 2.7=3.1.1
Python 2.7=3.1.2
Python 2.7=3.1.3
Python 2.7=3.1.4
Python 2.7=3.1.5
Python 2.7=3.2.0
Python 2.7=3.2.1
Python 2.7=3.2.2
Python 2.7=3.2.3
Python 2.7=3.2.4
Python 2.7=3.2.5
Python 2.7=3.2.6
Python 2.7=3.3.0
Python 2.7=3.3.1
Python 2.7=3.3.2
Python 2.7=3.3.3
Python 2.7=3.3.4
Python 2.7=3.3.5
Python 2.7=3.3.6
Python 2.7=3.4.0
Python 2.7=3.4.1
Python 2.7=3.4.2
Python 2.7=3.4.3

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Reference Links

Parent vulnerabilities

(Appears in the following advisories)

Frequently Asked Questions

  • What is the severity of CVE-2016-5699?

    CVE-2016-5699 has a medium severity level, allowing for the injection of additional HTTP headers in affected Python libraries.

  • How do I fix CVE-2016-5699?

    To fix CVE-2016-5699, upgrade your Python package to a version that includes the upstream patches addressing this vulnerability.

  • Which versions of Python are affected by CVE-2016-5699?

    CVE-2016-5699 affects multiple versions of Python, including versions prior to 2.7.9 and specific releases up to 3.5.1.

  • What libraries in Python does CVE-2016-5699 impact?

    CVE-2016-5699 specifically impacts the http, ftp, and url libraries within Python.

  • Is there a specific package recommended for CVE-2016-5699 remediation?

    Yes, updating to the specific recommended packages such as python-2.7.9 or later, python27-python-2.7.8-16.el7, or rh-python34-python-3.4.2-14.el6 is needed for remediation.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203