CWE
172
Advisory Published
CVE Published
Updated

CVE-2019-9636

First published: Wed Mar 06 2019(Updated: )

A vulnerability was found in Python 2.7.x through 2.7.16 and 3.x through 3.7.2. An improper Handling of Unicode Encoding (with an incorrect netloc) during NFKC normalization could lead to an Information Disclosure (credentials, cookies, etc. that are cached against a given hostname) in the urllib.parse.urlsplit, urllib.parse.urlparse components. A specially crafted URL could be incorrectly parsed to locate cookies or authentication data and send that information to a different host than when parsed correctly. References: <a href="https://bugs.python.org/issue36216">https://bugs.python.org/issue36216</a> <a href="https://python-security.readthedocs.io/vuln/urlsplit-nfkc-normalization.html">https://python-security.readthedocs.io/vuln/urlsplit-nfkc-normalization.html</a> Uptream Patch: <a href="https://github.com/python/cpython/pull/12201">https://github.com/python/cpython/pull/12201</a>

Credit: cve@mitre.org cve@mitre.org cve@mitre.org

Affected SoftwareAffected VersionHow to fix
redhat/python<0:2.6.6-68.el6_10
0:2.6.6-68.el6_10
redhat/python<0:2.7.5-77.el7_6
0:2.7.5-77.el7_6
redhat/python<0:2.7.5-59.el7_4
0:2.7.5-59.el7_4
redhat/python<0:2.7.5-70.el7_5
0:2.7.5-70.el7_5
redhat/python3<0:3.6.8-2.el8_0
0:3.6.8-2.el8_0
redhat/rh-python36-python<0:3.6.3-4.el6
0:3.6.3-4.el6
redhat/python27-python<0:2.7.13-4.el6
0:2.7.13-4.el6
redhat/rh-python35-python<0:3.5.1-12.el6
0:3.5.1-12.el6
redhat/rh-python36-python<0:3.6.3-7.el7
0:3.6.3-7.el7
redhat/python27-python<0:2.7.13-6.el7
0:2.7.13-6.el7
redhat/rh-python35-python<0:3.5.1-12.el7
0:3.5.1-12.el7
redhat/redhat-release-virtualization-host<0:4.2-8.4.el7
0:4.2-8.4.el7
redhat/redhat-virtualization-host<0:4.2-20190411.1.el7_6
0:4.2-20190411.1.el7_6
redhat/rhvm-appliance<0:4.2-20190411.1.el7
0:4.2-20190411.1.el7
redhat/python<3.5.7
3.5.7
redhat/python<3.7.3
3.7.3
debian/python2.7
2.7.18-8+deb11u1
Python Babel Localedata>=2.7.0<2.7.17
Python Babel Localedata>=3.0.0<3.4.10
Python Babel Localedata>=3.5.0<3.5.7
Python Babel Localedata>=3.6.0<3.6.9
Python Babel Localedata>=3.7.0<3.7.3
Fedoraproject Fedora=28
Fedoraproject Fedora=29
Fedoraproject Fedora=30
Fedoraproject Fedora=31
openSUSE=15.0
openSUSE=15.1
openSUSE=42.3
Debian GNU/Linux=8.0
Debian GNU/Linux=9.0
Ubuntu Linux=12.04
Ubuntu Linux=14.04
Ubuntu Linux=16.04
Ubuntu Linux=18.04
Ubuntu Linux=19.04
redhat openshift container platform=3.11
Red Hat Enterprise Linux=7.5
Red Hat Enterprise Linux=8.0
redhat enterprise Linux desktop=6.0
redhat enterprise Linux eus=7.5
redhat enterprise Linux eus=8.1
redhat enterprise Linux eus=8.2
redhat enterprise Linux eus=8.4
redhat enterprise Linux eus=8.6
redhat enterprise Linux server=6.0
redhat enterprise Linux server aus=7.4
redhat enterprise Linux server aus=8.2
redhat enterprise Linux server aus=8.4
redhat enterprise Linux server eus=5.6
redhat enterprise Linux server tus=7.4
redhat enterprise Linux server tus=8.2
redhat enterprise Linux server tus=8.4
redhat enterprise Linux server tus=8.6
redhat enterprise Linux workstation=6.0
All of
Red Hat Enterprise Virtualization=4.0
Red Hat Enterprise Linux=7.0
Oracle Sun ZFS Storage Appliance Kit software=8.8.6
Fedora=28
Fedora=29
Fedora=30
Fedora=31
Debian=8.0
Debian=9.0
Ubuntu=12.04
Ubuntu=14.04
Ubuntu=16.04
Ubuntu=18.04
Ubuntu=19.04
Red Hat Enterprise Virtualization=4.0
Red Hat Enterprise Linux=7.0

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

Frequently Asked Questions

  • What is the severity of CVE-2019-9636?

    CVE-2019-9636 is considered a moderate severity vulnerability due to potential information disclosure.

  • How do I fix CVE-2019-9636?

    To fix CVE-2019-9636, update to Python version 2.7.17 or higher, or 3.5.7, 3.6.9, or 3.7.3.

  • What systems are affected by CVE-2019-9636?

    CVE-2019-9636 affects Python versions 2.7.x from 2.7.0 to 2.7.16 and 3.x from 3.0.0 to 3.7.2.

  • What are the potential impacts of CVE-2019-9636?

    The potential impact of CVE-2019-9636 includes the disclosure of sensitive information such as credentials and cookies.

  • Is there a workaround for CVE-2019-9636?

    There is no recommended workaround for CVE-2019-9636, and users are encouraged to apply the updates as soon as possible.

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