Approved changes feed: RSS · Atom

cpe:2.3:a:djangoproject:django:1.10:*:*:*:*:*:*:*

part: a version: 1.10 update: *

VendorDjangoproject (070db687-4713-5da4-80b0-4a67baf0d0d4)
ProductDjango (b34a5fd0-fae8-5096-941f-bded7e4dd228)
Edition*
Language*
Software edition*
Target software*
Target hardware*
Other*
NotesImported from purl2cpe mapping

PURL mappings

PURLSourceLast updated
pkg:docker/django/django purl2cpe 2026-06-01 10:17:26.721521
pkg:github/django/django purl2cpe 2026-06-01 10:17:26.721524
pkg:pypi/django purl2cpe 2026-06-01 10:17:26.721525

Vulnerability references

IdentifiercpeApplicabilitySubmitteddb.gcve.eu detailsRationale
CVE:CVE-2016-9014 vulnerable 2026-06-08 05:08:22.419927 Details available
Django before 1.8.x before 1.8.16, 1.9.x before 1.9.11, and 1.10.x before 1.10.3, when settings.DEBUG is True, allow remote attackers to conduct DNS rebinding attacks by leveraging failure to validate the HTTP Host header against settings.ALLOWED_HOSTS.
Published: 2016-12-09T20:00:00.000Z
Updated: 2024-08-06T02:35:02.332Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2016-9013 vulnerable 2026-06-08 05:08:22.396503 Details available
Django 1.8.x before 1.8.16, 1.9.x before 1.9.11, and 1.10.x before 1.10.3 use a hardcoded password for a temporary database user created when running tests with an Oracle database, which makes it easier for remote attackers to obtain access to the database server by leveraging failure to manually specify a password in the database settings TEST dictionary.
Published: 2016-12-09T20:00:00.000Z
Updated: 2024-08-06T02:35:02.828Z
Reference links
Imported from gcve-enriched-dumps CVE data

Contribute

You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.