gsd-2019-12781
Vulnerability from gsd
Modified
2023-12-13 01:23
Details
An issue was discovered in Django 1.11 before 1.11.22, 2.1 before 2.1.10, and 2.2 before 2.2.3. An HTTP request is not redirected to HTTPS when the SECURE_PROXY_SSL_HEADER and SECURE_SSL_REDIRECT settings are used, and the proxy connects to Django via HTTPS. In other words, django.http.HttpRequest.scheme has incorrect behavior when a client uses HTTP.
Aliases
Aliases
{ GSD: { alias: "CVE-2019-12781", description: "An issue was discovered in Django 1.11 before 1.11.22, 2.1 before 2.1.10, and 2.2 before 2.2.3. An HTTP request is not redirected to HTTPS when the SECURE_PROXY_SSL_HEADER and SECURE_SSL_REDIRECT settings are used, and the proxy connects to Django via HTTPS. In other words, django.http.HttpRequest.scheme has incorrect behavior when a client uses HTTP.", id: "GSD-2019-12781", references: [ "https://www.suse.com/security/cve/CVE-2019-12781.html", "https://www.debian.org/security/2019/dsa-4476", "https://access.redhat.com/errata/RHSA-2020:4390", "https://access.redhat.com/errata/RHSA-2020:4366", "https://access.redhat.com/errata/RHSA-2020:1324", "https://ubuntu.com/security/CVE-2019-12781", "https://security.archlinux.org/CVE-2019-12781", ], }, gsd: { metadata: { exploitCode: "unknown", remediation: "unknown", reportConfidence: "confirmed", type: "vulnerability", }, osvSchema: { aliases: [ "CVE-2019-12781", ], details: "An issue was discovered in Django 1.11 before 1.11.22, 2.1 before 2.1.10, and 2.2 before 2.2.3. An HTTP request is not redirected to HTTPS when the SECURE_PROXY_SSL_HEADER and SECURE_SSL_REDIRECT settings are used, and the proxy connects to Django via HTTPS. In other words, django.http.HttpRequest.scheme has incorrect behavior when a client uses HTTP.", id: "GSD-2019-12781", modified: "2023-12-13T01:23:43.910413Z", schema_version: "1.4.0", }, }, namespaces: { "cve.org": { CVE_data_meta: { ASSIGNER: "cve@mitre.org", ID: "CVE-2019-12781", STATE: "PUBLIC", }, affects: { vendor: { vendor_data: [ { product: { product_data: [ { product_name: "n/a", version: { version_data: [ { version_value: "n/a", }, ], }, }, ], }, vendor_name: "n/a", }, ], }, }, data_format: "MITRE", data_type: "CVE", data_version: "4.0", description: { description_data: [ { lang: "eng", value: "An issue was discovered in Django 1.11 before 1.11.22, 2.1 before 2.1.10, and 2.2 before 2.2.3. An HTTP request is not redirected to HTTPS when the SECURE_PROXY_SSL_HEADER and SECURE_SSL_REDIRECT settings are used, and the proxy connects to Django via HTTPS. In other words, django.http.HttpRequest.scheme has incorrect behavior when a client uses HTTP.", }, ], }, problemtype: { problemtype_data: [ { description: [ { lang: "eng", value: "n/a", }, ], }, ], }, references: { reference_data: [ { name: "https://docs.djangoproject.com/en/dev/releases/security/", refsource: "MISC", url: "https://docs.djangoproject.com/en/dev/releases/security/", }, { name: "https://groups.google.com/forum/#!topic/django-announce/Is4kLY9ZcZQ", refsource: "MISC", url: "https://groups.google.com/forum/#!topic/django-announce/Is4kLY9ZcZQ", }, { name: "https://www.djangoproject.com/weblog/2019/jul/01/security-releases/", refsource: "CONFIRM", url: "https://www.djangoproject.com/weblog/2019/jul/01/security-releases/", }, { name: "[oss-security] 20190701 Django: CVE-2019-12781: Incorrect HTTP detection with reverse-proxy connecting via HTTPS", refsource: "MLIST", url: "http://www.openwall.com/lists/oss-security/2019/07/01/3", }, { name: "USN-4043-1", refsource: "UBUNTU", url: "https://usn.ubuntu.com/4043-1/", }, { name: "109018", refsource: "BID", url: "http://www.securityfocus.com/bid/109018", }, { name: "https://security.netapp.com/advisory/ntap-20190705-0002/", refsource: "CONFIRM", url: "https://security.netapp.com/advisory/ntap-20190705-0002/", }, { name: "DSA-4476", refsource: "DEBIAN", url: "https://www.debian.org/security/2019/dsa-4476", }, { name: "20190708 [SECURITY] [DSA 4476-1] python-django security update", refsource: "BUGTRAQ", url: "https://seclists.org/bugtraq/2019/Jul/10", }, { name: "FEDORA-2019-d9aa58d863", refsource: "FEDORA", url: "https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/5VXXWIOQGXOB7JCGJ3CVUW673LDHKEYL/", }, { name: "openSUSE-SU-2019:1839", refsource: "SUSE", url: "http://lists.opensuse.org/opensuse-security-announce/2019-08/msg00006.html", }, { name: "openSUSE-SU-2019:1872", refsource: "SUSE", url: "http://lists.opensuse.org/opensuse-security-announce/2019-08/msg00025.html", }, ], }, }, "gitlab.com": { advisories: [ { affected_range: ">=1.11,<1.11.22||>=2.1,<2.1.10||>=2.2,<2.2.3", affected_versions: "All versions starting from 1.11 before 1.11.22, all versions starting from 2.1 before 2.1.10, all versions starting from 2.2 before 2.2.3", cvss_v2: "AV:N/AC:L/Au:N/C:P/I:N/A:N", cvss_v3: "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N", cwe_ids: [ "CWE-1035", "CWE-319", "CWE-937", ], date: "2019-07-13", description: "An HTTP request is not redirected to HTTPS when the `SECURE_PROXY_SSL_HEADER` and `SECURE_SSL_REDIRECT` settings are used, and the proxy connects to Django via HTTPS. In other words, `django.http.HttpRequest.scheme` has incorrect behavior when a client uses HTTP.", fixed_versions: [ "1.11.22", "2.1.10", "2.2.3", ], identifier: "CVE-2019-12781", identifiers: [ "CVE-2019-12781", ], not_impacted: "All versions before 1.11, all versions starting from 1.11.22 before 2.1, all versions starting from 2.1.10 before 2.2, all versions starting from 2.2.3", package_slug: "pypi/Django", pubdate: "2019-07-01", solution: "Upgrade to versions 1.11.22, 2.1.10, 2.2.3 or above.", title: "Improper Input Validation", urls: [ "https://nvd.nist.gov/vuln/detail/CVE-2019-12781", "https://docs.djangoproject.com/en/dev/releases/security/", "https://www.djangoproject.com/weblog/2019/jul/01/security-releases/", ], uuid: "42367e41-2c04-4f04-bdaa-ea72d0957ef8", }, ], }, "nvd.nist.gov": { configurations: { CVE_data_version: "4.0", nodes: [ { children: [], cpe_match: [ { cpe23Uri: "cpe:2.3:a:djangoproject:django:*:*:*:*:*:*:*:*", cpe_name: [], versionEndExcluding: "2.1.10", versionStartIncluding: "2.1", vulnerable: true, }, { cpe23Uri: "cpe:2.3:a:djangoproject:django:*:*:*:*:*:*:*:*", cpe_name: [], versionEndExcluding: "2.2.3", versionStartIncluding: "2.2", vulnerable: true, }, { cpe23Uri: "cpe:2.3:a:djangoproject:django:*:*:*:*:*:*:*:*", cpe_name: [], versionEndExcluding: "1.11.22", versionStartIncluding: "1.11", vulnerable: true, }, ], operator: "OR", }, { children: [], cpe_match: [ { cpe23Uri: "cpe:2.3:o:canonical:ubuntu_linux:18.10:*:*:*:*:*:*:*", cpe_name: [], vulnerable: true, }, { cpe23Uri: "cpe:2.3:o:debian:debian_linux:9.0:*:*:*:*:*:*:*", cpe_name: [], vulnerable: true, }, { cpe23Uri: "cpe:2.3:o:canonical:ubuntu_linux:16.04:*:*:*:lts:*:*:*", cpe_name: [], vulnerable: true, }, { cpe23Uri: "cpe:2.3:o:canonical:ubuntu_linux:18.04:*:*:*:lts:*:*:*", cpe_name: [], vulnerable: true, }, { cpe23Uri: "cpe:2.3:o:canonical:ubuntu_linux:19.04:*:*:*:*:*:*:*", cpe_name: [], vulnerable: true, }, ], operator: "OR", }, ], }, cve: { CVE_data_meta: { ASSIGNER: "cve@mitre.org", ID: "CVE-2019-12781", }, data_format: "MITRE", data_type: "CVE", data_version: "4.0", description: { description_data: [ { lang: "en", value: "An issue was discovered in Django 1.11 before 1.11.22, 2.1 before 2.1.10, and 2.2 before 2.2.3. An HTTP request is not redirected to HTTPS when the SECURE_PROXY_SSL_HEADER and SECURE_SSL_REDIRECT settings are used, and the proxy connects to Django via HTTPS. In other words, django.http.HttpRequest.scheme has incorrect behavior when a client uses HTTP.", }, ], }, problemtype: { problemtype_data: [ { description: [ { lang: "en", value: "CWE-319", }, ], }, ], }, references: { reference_data: [ { name: "https://groups.google.com/forum/#!topic/django-announce/Is4kLY9ZcZQ", refsource: "MISC", tags: [ "Third Party Advisory", ], url: "https://groups.google.com/forum/#!topic/django-announce/Is4kLY9ZcZQ", }, { name: "https://www.djangoproject.com/weblog/2019/jul/01/security-releases/", refsource: "CONFIRM", tags: [ "Patch", "Vendor Advisory", ], url: "https://www.djangoproject.com/weblog/2019/jul/01/security-releases/", }, { name: "https://docs.djangoproject.com/en/dev/releases/security/", refsource: "MISC", tags: [ "Patch", "Vendor Advisory", ], url: "https://docs.djangoproject.com/en/dev/releases/security/", }, { name: "[oss-security] 20190701 Django: CVE-2019-12781: Incorrect HTTP detection with reverse-proxy connecting via HTTPS", refsource: "MLIST", tags: [ "Mailing List", "Patch", "Third Party Advisory", ], url: "http://www.openwall.com/lists/oss-security/2019/07/01/3", }, { name: "USN-4043-1", refsource: "UBUNTU", tags: [ "Third Party Advisory", ], url: "https://usn.ubuntu.com/4043-1/", }, { name: "109018", refsource: "BID", tags: [ "Third Party Advisory", ], url: "http://www.securityfocus.com/bid/109018", }, { name: "https://security.netapp.com/advisory/ntap-20190705-0002/", refsource: "CONFIRM", tags: [ "Third Party Advisory", ], url: "https://security.netapp.com/advisory/ntap-20190705-0002/", }, { name: "DSA-4476", refsource: "DEBIAN", tags: [ "Third Party Advisory", ], url: "https://www.debian.org/security/2019/dsa-4476", }, { name: "20190708 [SECURITY] [DSA 4476-1] python-django security update", refsource: "BUGTRAQ", tags: [ "Third Party Advisory", ], url: "https://seclists.org/bugtraq/2019/Jul/10", }, { name: "FEDORA-2019-d9aa58d863", refsource: "FEDORA", tags: [], url: "https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/5VXXWIOQGXOB7JCGJ3CVUW673LDHKEYL/", }, { name: "openSUSE-SU-2019:1839", refsource: "SUSE", tags: [], url: "http://lists.opensuse.org/opensuse-security-announce/2019-08/msg00006.html", }, { name: "openSUSE-SU-2019:1872", refsource: "SUSE", tags: [], url: "http://lists.opensuse.org/opensuse-security-announce/2019-08/msg00025.html", }, ], }, }, impact: { baseMetricV2: { acInsufInfo: false, cvssV2: { accessComplexity: "LOW", accessVector: "NETWORK", authentication: "NONE", availabilityImpact: "NONE", baseScore: 5, confidentialityImpact: "PARTIAL", integrityImpact: "NONE", vectorString: "AV:N/AC:L/Au:N/C:P/I:N/A:N", version: "2.0", }, exploitabilityScore: 10, impactScore: 2.9, obtainAllPrivilege: false, obtainOtherPrivilege: false, obtainUserPrivilege: false, severity: "MEDIUM", userInteractionRequired: false, }, baseMetricV3: { cvssV3: { attackComplexity: "LOW", attackVector: "NETWORK", availabilityImpact: "NONE", baseScore: 5.3, baseSeverity: "MEDIUM", confidentialityImpact: "LOW", integrityImpact: "NONE", privilegesRequired: "NONE", scope: "UNCHANGED", userInteraction: "NONE", vectorString: "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N", version: "3.0", }, exploitabilityScore: 3.9, impactScore: 1.4, }, }, lastModifiedDate: "2020-08-24T17:37Z", publishedDate: "2019-07-01T14:15Z", }, }, }
Log in or create an account to share your comment.
Security Advisory comment format.
This schema specifies the format of a comment related to a security advisory.
Title of the comment
Description of the comment
Loading…
Loading…
Loading…
Sightings
Author | Source | Type | Date |
---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.