Bugs fixes in "python-django"
| Origin | Bug number | Title | Date fixed |
|---|---|---|---|
| CVE | CVE-2019-14233 | RESERVED | 2019-08-01 |
| CVE | CVE-2019-14232 | RESERVED | 2019-08-01 |
| CVE | CVE-2019-14235 | RESERVED | 2019-08-01 |
| CVE | CVE-2019-14234 | RESERVED | 2019-08-01 |
| CVE | CVE-2019-14233 | RESERVED | 2019-08-01 |
| CVE | CVE-2019-14232 | RESERVED | 2019-08-01 |
| CVE | CVE-2019-14235 | RESERVED | 2019-08-01 |
| CVE | CVE-2019-14234 | RESERVED | 2019-08-01 |
| CVE | CVE-2019-14233 | RESERVED | 2019-08-01 |
| CVE | CVE-2019-14232 | RESERVED | 2019-08-01 |
| CVE | CVE-2019-12781 | Incorrect HTTP detection with reverse-proxy connecting via HTTPS | 2019-07-03 |
| CVE | CVE-2019-12781 | Incorrect HTTP detection with reverse-proxy connecting via HTTPS | 2019-07-02 |
| CVE | CVE-2019-12781 | Incorrect HTTP detection with reverse-proxy connecting via HTTPS | 2019-07-01 |
| CVE | CVE-2019-12781 | Incorrect HTTP detection with reverse-proxy connecting via HTTPS | 2019-07-01 |
| CVE | CVE-2019-6975 | Django 1.11.x before 1.11.19, 2.0.x before 2.0.11, and 2.1.x before 2.1.6 allows Uncontrolled Memory Consumption via a malicious attacker-supplied va | 2019-02-13 |
| CVE | CVE-2019-6975 | Django 1.11.x before 1.11.19, 2.0.x before 2.0.11, and 2.1.x before 2.1.6 allows Uncontrolled Memory Consumption via a malicious attacker-supplied va | 2019-02-13 |
| CVE | CVE-2019-6975 | Django 1.11.x before 1.11.19, 2.0.x before 2.0.11, and 2.1.x before 2.1.6 allows Uncontrolled Memory Consumption via a malicious attacker-supplied va | 2019-02-13 |
| CVE | CVE-2019-6975 | Django 1.11.x before 1.11.19, 2.0.x before 2.0.11, and 2.1.x before 2.1.6 allows Uncontrolled Memory Consumption via a malicious attacker-supplied va | 2019-02-13 |
| CVE | CVE-2019-3498 | Content spoofing possibility in the default 404 page | 2019-01-10 |
| CVE | CVE-2019-3498 | Content spoofing possibility in the default 404 page | 2019-01-09 |
About
-
Send Feedback to @ubuntu_updates
