Quick answers
- Is CVE-2017-7233 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2017-7233 being exploited in the wild.
- How severe is CVE-2017-7233?
- Low severity, with a CVSS score of 3, published 4 April 2017.
- Which products and versions are affected?
- Django (PyPI) ECOSYSTEM:introduced=1.10,fixed=1.10.7,introduced=1.9,fixed=1.9.13,introduced=1.8,fixed=1.8.18, ECOSYSTEM:introduced=1.10a1,fixed=1.10.7.
- Is there a fix for CVE-2017-7233?
- Yes. Django (PyPI): upgrade to 1.10.7, 1.8.18 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2017-7233 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2017-7233?
- Check whether you run Django (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Django (PyPI): upgrade to 1.10.7, 1.8.18 or later
pip install "Django>=1.10.7"
Technical details
The vulnerability exists in Django's is_safe_url() validation function, which is used to check whether redirect URLs are safe before sending users to them. The function incorrectly classified certain numeric URLs as safe, violating the CWE-601 (Open Redirect) vulnerability class. An attacker can craft a numeric redirect URL to bypass the validation, enabling open redirect attacks. Additionally, if developers embed these URLs directly in HTML links without additional sanitization, reflected XSS is possible. No authentication is required; the attack leverages user interaction (clicking a malicious link). Patches were released in Django 1.8.18, 1.9.13, and 1.10.7.
Affected products
- Django Django 1.8 before 1.8.18, 1.9 before 1.9.13, 1.10 before 1.10.7
Identifiers
- CVE-2017-7233
- GHSA-37hp-765x-j95x
- PYSEC-2017-9
Timeline
- 2017-04-04: disclosed
- 2017-04-04: patched