CVE-2020-13254
published 2020-06-03CVE-2020-13254: An issue was discovered in Django 2.2 before 2.2.13 and 3.0 before 3.0.7. In cases where a memcached backend does not perform key validation, passing malformed…
PriorityP335medium5.9CVSS 3.1
AVNACHPRNUINSUCHINAN
EPSS
6.09%
92.6th percentile
An issue was discovered in Django 2.2 before 2.2.13 and 3.0 before 3.0.7. In cases where a memcached backend does not perform key validation, passing malformed cache keys could result in a key collision, and potential data leakage.
Affected
15 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| canonical | ubuntu_linux | — | — |
| canonical | ubuntu_linux | — | — |
| canonical | ubuntu_linux | — | — |
| canonical | ubuntu_linux | — | — |
| canonical | ubuntu_linux | — | — |
| debian | debian_linux | — | — |
| debian | debian_linux | — | — |
| debian | debian_linux | — | — |
| debian | python-django | < python-django 2:2.2.13-1 (bookworm) | python-django 2:2.2.13-1 (bookworm) |
| djangoproject | django | >= 2.2 < 2.2.13 | 2.2.13 |
| djangoproject | django | >= 2.2 < 2.2.13 | 2.2.13 |
| djangoproject | django | >= 3.0 < 3.0.7 | 3.0.7 |
| djangoproject | django | >= 3.0 < 3.0.7 | 3.0.7 |
| fedoraproject | fedora | — | — |
| oracle | zfs_storage_appliance_kit | — | — |
CVSS provenance
nvdv3.15.9MEDIUMCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
nvdv2.04.3MEDIUMAV:N/AC:M/Au:N/C:P/I:N/A:N
osv5.9MEDIUM
vendor_debian5.9MEDIUM
vendor_redhat5.9MEDIUM
vendor_ubuntu5.9MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
OSV
Data leakage via cache key collision in Django
osv·2020-06-05
CVE-2020-13254 [HIGH] Data leakage via cache key collision in Django
Data leakage via cache key collision in Django
An issue was discovered in Django version 2.2 before 2.2.13 and 3.0 before 3.0.7. In cases where a memcached backend does not perform key validation, passing malformed cache keys could result in a key collision, and potential data leakage.
GHSA
Data leakage via cache key collision in Django
ghsa·2020-06-05
CVE-2020-13254 [HIGH] CWE-295 Data leakage via cache key collision in Django
Data leakage via cache key collision in Django
An issue was discovered in Django version 2.2 before 2.2.13 and 3.0 before 3.0.7. In cases where a memcached backend does not perform key validation, passing malformed cache keys could result in a key collision, and potential data leakage.
OSV
python-django vulnerabilities
osv·2020-06-04·CVSS 5.9
CVE-2020-13254 [MEDIUM] python-django vulnerabilities
python-django vulnerabilities
USN-4381-1 fixed several vulnerabilities in Django. This update provides
the corresponding update for Ubuntu 14.04 ESM.
Original advisory details:
Dan Palmer discovered that Django incorrectly validated memcached cache
keys. A remote attacker could possibly use this issue to cause a denial of
service and obtain sensitive information. (CVE-2020-13254)
Jon Dufresne discovered that Django incorrectly encoded query parameters
for the admin ForeignKeyRawIdWidget. A remote attacker could possibly use
this issue to perform XSS attacks. (CVE-2020-13596)
OSV
python-django vulnerabilities
osv·2020-06-03·CVSS 5.9
CVE-2020-13254 [MEDIUM] python-django vulnerabilities
python-django vulnerabilities
Dan Palmer discovered that Django incorrectly validated memcached cache
keys. A remote attacker could possibly use this issue to cause a denial of
service and obtain sensitive information. (CVE-2020-13254)
Jon Dufresne discovered that Django incorrectly encoded query parameters
for the admin ForeignKeyRawIdWidget. A remote attacker could possibly use
this issue to perform XSS attacks. (CVE-2020-13596)
OSV
CVE-2020-13254: An issue was discovered in Django 2
osv·2020-06-03·CVSS 5.9
CVE-2020-13254 [MEDIUM] CVE-2020-13254: An issue was discovered in Django 2
An issue was discovered in Django 2.2 before 2.2.13 and 3.0 before 3.0.7. In cases where a memcached backend does not perform key validation, passing malformed cache keys could result in a key collision, and potential data leakage.
Ubuntu
Django vulnerabilities
vendor_ubuntu·2020-06-04·CVSS 5.9
CVE-2020-13254 [MEDIUM] Django vulnerabilities
Title: Django vulnerabilities
Summary: Several security issues were fixed in Django.
USN-4381-1 fixed several vulnerabilities in Django. This update provides
the corresponding update for Ubuntu 14.04 ESM.
Original advisory details:
Dan Palmer discovered that Django incorrectly validated memcached cache
keys. A remote attacker could possibly use this issue to cause a denial of
service and obtain sensitive information. (CVE-2020-13254)
Jon Dufresne discovered that Django incorrectly encoded query parameters
for the admin ForeignKeyRawIdWidget. A remote attacker could possibly use
this issue to perform XSS attacks. (CVE-2020-13596)
Instructions: In general, a standard system update will make all the necessary changes.
Ubuntu
Django vulnerabilities
vendor_ubuntu·2020-06-03·CVSS 5.9
CVE-2020-13254 [MEDIUM] Django vulnerabilities
Title: Django vulnerabilities
Summary: Several security issues were fixed in Django.
Dan Palmer discovered that Django incorrectly validated memcached cache
keys. A remote attacker could possibly use this issue to cause a denial of
service and obtain sensitive information. (CVE-2020-13254)
Jon Dufresne discovered that Django incorrectly encoded query parameters
for the admin ForeignKeyRawIdWidget. A remote attacker could possibly use
this issue to perform XSS attacks. (CVE-2020-13596)
Instructions: In general, a standard system update will make all the necessary changes.
Red Hat
django: potential data leakage via malformed memcached keys
vendor_redhat·2020-06-03·CVSS 5.9
CVE-2020-13254 [MEDIUM] CWE-20 django: potential data leakage via malformed memcached keys
django: potential data leakage via malformed memcached keys
An issue was discovered in Django 2.2 before 2.2.13 and 3.0 before 3.0.7. In cases where a memcached backend does not perform key validation, passing malformed cache keys could result in a key collision, and potential data leakage.
A flaw was found in Django, where the memcached backend does not perform key validation and passes malformed keys. This flaw causes a key collision and potential data leakage. The highest threat from this vulnerability is to confidentiality.
Statement: Red Hat Satellite 6 ships affected python-django, however, it does not use memcached implementation in product code hence not vulnerable to this flaw.
Red Hat Update Infrastructure 3 ships an affected version of python-django, however it does not use m
Debian
CVE-2020-13254: python-django - An issue was discovered in Django 2.2 before 2.2.13 and 3.0 before 3.0.7. In cas...
vendor_debian·2020·CVSS 5.9
CVE-2020-13254 [MEDIUM] CVE-2020-13254: python-django - An issue was discovered in Django 2.2 before 2.2.13 and 3.0 before 3.0.7. In cas...
An issue was discovered in Django 2.2 before 2.2.13 and 3.0 before 3.0.7. In cases where a memcached backend does not perform key validation, passing malformed cache keys could result in a key collision, and potential data leakage.
Scope: local
bookworm: resolved (fixed in 2:2.2.13-1)
bullseye: resolved (fixed in 2:2.2.13-1)
forky: resolved (fixed in 2:2.2.13-1)
sid: resolved (fixed in 2:2.2.13-1)
trixie: resolved (fixed in 2:2.2.13-1)
No detection rules found.
No public exploits indexed.
Bugzilla
CVE-2020-13254 python2-django1.11: django: potential data leakage via malformed memcached keys [fedora-all]
bugzilla·2020-06-09·CVSS 5.9
CVE-2020-13254 [MEDIUM] CVE-2020-13254 python2-django1.11: django: potential data leakage via malformed memcached keys [fedora-all]
CVE-2020-13254 python2-django1.11: django: potential data leakage via malformed memcached keys [fedora-all]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of fedora-all.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
NOTE: this issue affec
Bugzilla
CVE-2020-13254 python-django: django: potential data leakage via malformed memcached keys [epel-all]
bugzilla·2020-06-03·CVSS 5.9
CVE-2020-13254 [MEDIUM] CVE-2020-13254 python-django: django: potential data leakage via malformed memcached keys [epel-all]
CVE-2020-13254 python-django: django: potential data leakage via malformed memcached keys [epel-all]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of epel-all.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
NOTE: this issue affects multip
Bugzilla
CVE-2020-13254 python-django: django: potential data leakage via malformed memcached keys [openstack-rdo]
bugzilla·2020-06-03·CVSS 5.9
CVE-2020-13254 [MEDIUM] CVE-2020-13254 python-django: django: potential data leakage via malformed memcached keys [openstack-rdo]
CVE-2020-13254 python-django: django: potential data leakage via malformed memcached keys [openstack-rdo]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of openstack-rdo.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
Discussion:
All RDO
Bugzilla
CVE-2020-13254 python-django16: django: potential data leakage via malformed memcached keys [epel-7]
bugzilla·2020-06-03·CVSS 5.9
CVE-2020-13254 [MEDIUM] CVE-2020-13254 python-django16: django: potential data leakage via malformed memcached keys [epel-7]
CVE-2020-13254 python-django16: django: potential data leakage via malformed memcached keys [epel-7]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of epel-7.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
Discussion:
Use the following te
Bugzilla
CVE-2020-13254 django: potential data leakage via malformed memcached keys
bugzilla·2020-06-03·CVSS 5.9
CVE-2020-13254 [MEDIUM] CVE-2020-13254 django: potential data leakage via malformed memcached keys
CVE-2020-13254 django: potential data leakage via malformed memcached keys
In cases where a memcached backend does not perform key validation, passing malformed cache keys could result in a key collision, and potential data leakage. In order to avoid this vulnerability, key validation is added to the memcached cache backends.
Reference:
https://www.djangoproject.com/weblog/2020/jun/03/security-releases/
Discussion:
Created django:1.6/python-django tracking bugs for this issue:
Affects: fedora-all [bug 1843620]
Created python-django tracking bugs for this issue:
Affects: epel-all [bug 1843616]
Affects: fedora-all [bug 1843617]
Affects: openstack-rdo [bug 1843619]
Created python-django16 tracking bugs for this issue:
Affects: epel-7 [bug 1843618]
---
External References:
https:
Bugzilla
CVE-2020-13254 python-django: django: potential data leakage via malformed memcached keys [fedora-all]
bugzilla·2020-06-03·CVSS 5.9
CVE-2020-13254 [MEDIUM] CVE-2020-13254 python-django: django: potential data leakage via malformed memcached keys [fedora-all]
CVE-2020-13254 python-django: django: potential data leakage via malformed memcached keys [fedora-all]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of fedora-all.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
NOTE: this issue affects mu
Bugzilla
CVE-2020-13254 django:1.6/python-django: django: potential data leakage via malformed memcached keys [fedora-all]
bugzilla·2020-06-03·CVSS 5.9
CVE-2020-13254 [MEDIUM] CVE-2020-13254 django:1.6/python-django: django: potential data leakage via malformed memcached keys [fedora-all]
CVE-2020-13254 django:1.6/python-django: django: potential data leakage via malformed memcached keys [fedora-all]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of fedora-all.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
NOTE: this issue
https://docs.djangoproject.com/en/3.0/releases/security/https://groups.google.com/d/msg/django-announce/pPEmb2ot4Fo/X-SMalYSBAAJhttps://lists.debian.org/debian-lts-announce/2020/06/msg00016.htmlhttps://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/4A2AP4T7RKPBCLTI2NNQG3T6MINDUUMZ/https://security.netapp.com/advisory/ntap-20200611-0002/https://usn.ubuntu.com/4381-1/https://usn.ubuntu.com/4381-2/https://www.debian.org/security/2020/dsa-4705https://www.djangoproject.com/weblog/2020/jun/03/security-releases/https://www.oracle.com/security-alerts/cpujan2021.htmlhttps://docs.djangoproject.com/en/3.0/releases/security/https://groups.google.com/d/msg/django-announce/pPEmb2ot4Fo/X-SMalYSBAAJhttps://lists.debian.org/debian-lts-announce/2020/06/msg00016.htmlhttps://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/4A2AP4T7RKPBCLTI2NNQG3T6MINDUUMZ/https://security.netapp.com/advisory/ntap-20200611-0002/https://usn.ubuntu.com/4381-1/https://usn.ubuntu.com/4381-2/https://www.debian.org/security/2020/dsa-4705https://www.djangoproject.com/weblog/2020/jun/03/security-releases/https://www.oracle.com/security-alerts/cpujan2021.html
2020-06-03
Published