CVE-2020-13254

medium
Published 2020-06-05 ยท Modified 2023-12-06
CVSS v3
โ€”
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
CVSS v4 NEW
โ€”
not yet in upstream
VIR risk
5.5

Description

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.

Predictions

Exploit likelihood
30%
Patch ETA
โ€”

Heuristic predictions, AS-IS, for prioritization only.

Mitigations

No mitigations published for this CVE yet.

The vendor-content worker queues fetches as references arrive (check back in a few minutes). Or โ€” if you've already worked around this in production โ€” publish your fix to the community-verified tier.

โœš Propose a mitigation on Community โ†’ Mitigations published via the community go through AI scoring + 2 human reviewers + 7-day silent objection window before landing here with source_tier=community-verified.

OS impact

arch Arch Fixed 1 release
VersionStatusFixed in
โ€” Fixed 3.0.7-1
debian Debian Fixed 5 releases
VersionStatusFixed in
trixie Fixed 2:2.2.13-1
sid Fixed 2:2.2.13-1
forky Fixed 2:2.2.13-1
bullseye Fixed 2:2.2.13-1
bookworm Fixed 2:2.2.13-1

Package impact

EcosystemPackageVulnerableFixed
python PyPIdjango>=2.2,<2.2.132.2.13
python PyPIdjango>=3.0,<3.0.73.0.7

References

Community-verified mitigations for this CVE will appear above when contributors publish them.

Verify integrity in audit chain (admin only). AS-IS.