An issue was discovered in Django 1.11 before 1.11.21, 2.1 before 2.1.9, and 2.2 before 2.2.2. The clickable Current URL value displayed by the AdminURLFieldWidget displays the provided value without validating it as a safe URL. Thus, an unvalidated value stored in the database, or a value provided as a URL query parameter payload, could result in an clickable JavaScript link.

The remote openSUSE 15 host has a package installed that is affected by multiple vulnerabilities as referenced in the SUSE-SU-2024:2817-1 advisory.

    - CVE-2024-42005: Fixed SQL injection in QuerySet.values() and values_list() (bsc#1228629)
    - CVE-2024-41989: Fixed Memory exhaustion in django.utils.numberformat.floatformat() (bsc#1228630)
    - CVE-2024-41990: Fixed denial-of-service vulnerability in django.utils.html.urlize() (bsc#1228631)
    - CVE-2024-41991: Fixed another denial-of-service vulnerability in django.utils.html.urlize()     (bsc#1228632)
    - CVE-2022-28346: Fixed SQL injection in QuerySet.annotate(),aggregate() and extra() (bsc#1198398)
    - CVE-2019-12308: Fixed XSS in AdminURLFieldWidget (bsc#1136468)

Tenable has extracted the preceding description block directly from the SUSE security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote host is affected by the vulnerability described in GLSA-202004-17 (Django: Multiple vulnerabilities)

    Multiple vulnerabilities have been discovered in Django. Please review       the CVE identifiers referenced below for details.
  Impact :

    A remote attacker, by sending specially crafted input, could possibly       cause a Denial of Service condition, or alter the database.
  Workaround :

    There is no known workaround at this time.

This update for python-Django fixes the following issues :

Security issues fixed :

&#9; - CVE-2019-11358: Fixed prototype pollution.

  - CVE-2019-12308: Fixed XSS in AdminURLFieldWidget     (bsc#1136468)

  - CVE-2019-12781: Fixed incorrect HTTP detection with     reverse-proxy connecting via HTTPS (bsc#1139945).

  - CVE-2019-14232: Fixed denial-of-service possibility in     ``django.utils.text.Truncator`` (bsc#1142880).

  - CVE-2019-14233: Fixed denial-of-service possibility in     ``strip_tags()`` (bsc#1142882).

  - CVE-2019-14234: Fixed SQL injection possibility in key     and index lookups for ``JSONField``/``HStoreField``     (bsc#1142883).

  - CVE-2019-14235: Fixed potential memory exhaustion in     ``django.utils.encoding.uri_to_iri()`` (bsc#1142885).

Non-security issues fixed :

  - Fixed a migration crash on PostgreSQL when adding a     check constraint with a contains lookup on     DateRangeField or DateTimeRangeField, if the right hand     side of an expression is the same type.

Three security issues were found in Django, a Python web development framework, which could result in denial of service, incomplete sanitisation of clickable links or missing redirects of HTTP requests to HTTPS.

The remote Ubuntu 16.04 LTS / 18.04 LTS host has packages installed that are affected by multiple vulnerabilities as referenced in the USN-4043-1 advisory.

    It was discovered that Django incorrectly handled certain inputs. An attacker could possibly use this     issue to execute arbitrary code. This issue only affected Ubuntu 18.04 LTS, Ubuntu 18.10 and Ubuntu 19.04.
    (CVE-2019-12308)

    Gavin Wahl discovered that Django incorrectly handled HTTP detection when used behind a reverse-proxy.
    Client requests made via HTTP would cause incorrect API results and would not be redirected to HTTPS,     contrary to expectations. (CVE-2019-12781)

Tenable has extracted the preceding description block directly from the Ubuntu security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

It was discovered that the Django Python web development framework did not correct identify HTTP connections when a reverse proxy connected via HTTPS.

When deployed behind a reverse-proxy connecting to Django via HTTPS django.http.HttpRequest.scheme would incorrectly detect client requests made via HTTP as using HTTPS. This resulted in incorrect results for is_secure(), and build_absolute_uri(), and that HTTP requests would not be redirected to HTTPS in accordance with SECURE_SSL_REDIRECT.

HttpRequest.scheme now respects SECURE_PROXY_SSL_HEADER, if it is configured, and the appropriate header is set on the request, for both HTTP and HTTPS requests.

If you deploy Django behind a reverse-proxy that forwards HTTP requests, and that connects to Django via HTTPS, be sure to verify that your application correctly handles code paths relying on scheme, is_secure(), build_absolute_uri(), and SECURE_SSL_REDIRECT.

For Debian 8 'Jessie', this issue has been fixed in python-django version 1.7.11-1+deb8u6.

We recommend that you upgrade your python-django packages.

NOTE: Tenable Network Security has extracted the preceding description block directly from the DLA security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

update to 2.1.9

Note that Tenable Network Security has extracted the preceding description block directly from the Fedora update system website.
Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

Django security releases issued :

The clickable 'Current URL' link generated by AdminURLFieldWidget displayed the provided value without validating it as a safe URL.
Thus, an unvalidated value stored in the database, or a value provided as a URL query parameter payload, could result in an clickable JavaScript link..

jQuery before 3.4.0, mishandles jQuery.extend(true, {}, ...) because of Object.prototype pollution. If an unsanitized source object contained an enumerable __proto__ property, it could extend the native Object.prototype.

It was discovered that there was a cross-site scripting (XSS) vulnerability in the Django web development framework.

For Debian 8 'Jessie', this issue has been fixed in python-django version 1.7.11-1+deb8u5.

We recommend that you upgrade your python-django packages.

NOTE: Tenable Network Security has extracted the preceding description block directly from the DLA security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

ID	Name	Product	Family	Severity
205169	openSUSE 15 Security Update : python-Django (SUSE-SU-2024:2817-1)	Nessus	SuSE Local Security Checks	critical
136216	GLSA-202004-17 : Django: Multiple vulnerabilities	Nessus	Gentoo Local Security Checks	critical
127742	openSUSE Security Update : python-Django (openSUSE-2019-1839)	Nessus	SuSE Local Security Checks	critical
126514	Debian DSA-4476-1 : python-django - security update	Nessus	Debian Local Security Checks	medium
126445	Ubuntu 16.04 LTS / 18.04 LTS : Django vulnerabilities (USN-4043-1)	Nessus	Ubuntu Local Security Checks	medium
126390	Debian DLA-1842-1 : python-django security update	Nessus	Debian Local Security Checks	medium
125861	Fedora 30 : python-django (2019-57a4324120)	Nessus	Fedora Local Security Checks	medium
125750	FreeBSD : Django -- AdminURLFieldWidget XSS (ffc73e87-87f0-11e9-ad56-fcaa147e860e)	Nessus	FreeBSD Local Security Checks	medium
125740	Debian DLA-1814-1 : python-django security update	Nessus	Debian Local Security Checks	medium

Detections

Analytics

CVE-2019-12308

medium

Tenable Plugins

critical

critical

critical

medium

medium

medium

medium

medium

medium