Is CVE-2011-0697 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2011-0697 being exploited in the wild.

How severe is CVE-2011-0697?

Medium severity, with a CVSS score of 6.1, published 23 July 2018.

Which products and versions are affected?

Django (PyPI) ECOSYSTEM:introduced=1.1,fixed=1.1.4, ECOSYSTEM:introduced=1.1,fixed=1.1.4,introduced=1.2,fixed=1.2.5, ECOSYSTEM:introduced=1.1,fixed=1.1.4|ECOSYSTEM:introduced=1.2,fixed=1.2.5.

Is there a fix for CVE-2011-0697?

Yes. Django (PyPI): upgrade to 1.1.4, 1.2.5 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2011-0697 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2011-0697?

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.

CVE-2011-0697: Django cross-site scripting via file upload filename

CVE-2011-0697 · Severity: medium · CVSS 6.1 · Published 2018-07-23

Django is a popular web framework used to build and manage websites. A security flaw in older versions could allow an attacker to execute malicious scripts in a user's browser by uploading a file with a specially crafted name. This could lead to unauthorized actions being performed on behalf of users or the theft of sensitive session information.

Technologies: Django (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2011-0697 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2011-0697 being exploited in the wild.
How severe is CVE-2011-0697?: Medium severity, with a CVSS score of 6.1, published 23 July 2018.
Which products and versions are affected?: Django (PyPI) ECOSYSTEM:introduced=1.1,fixed=1.1.4, ECOSYSTEM:introduced=1.1,fixed=1.1.4,introduced=1.2,fixed=1.2.5, ECOSYSTEM:introduced=1.1,fixed=1.1.4|ECOSYSTEM:introduced=1.2,fixed=1.2.5.
Is there a fix for CVE-2011-0697?: Yes. Django (PyPI): upgrade to 1.1.4, 1.2.5 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2011-0697 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2011-0697?: 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.1.4, 1.2.5 or later
```
pip install "Django>=1.2.5"
```

Technical details

A cross-site scripting (XSS) vulnerability exists in Django's file upload handling. The root cause is the improper neutralization of input when processing filenames associated with uploaded files. A remote, unauthenticated attacker can exploit this by uploading a file with a malicious payload in its filename; if this filename is subsequently rendered in a web page without proper escaping, the script will execute in the context of the victim's browser. This requires minimal user interaction (viewing the page where the filename is displayed). The issue is resolved in Django versions 1.1.4 and 1.2.5.

Affected products

Django Django >= 1.1, < 1.1.4; >= 1.2, < 1.2.5

Identifiers

CVE-2011-0697
GHSA-8m3r-rv5g-fcpq
PYSEC-2011-11
PYSEC-2011-31

Timeline

2011-02-08: advisory: Original Django security release announcement
2011-02-14: disclosed: NVD publication date
2018-07-23: advisory: GitHub Advisory Database publication

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.