Potential Observable Timing Discrepancy in Wagtail
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 2.7.3, 2.8.2, 2.9
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
In Wagtail before versions 2.7.3 and 2.8.2, a potential timing attack exists on pages or documents that have been protected with a shared password through Wagtail's "Privacy" controls. This password check is performed through a character-by-character string comparison, and so an attacker who is able to measure the time taken by this check to a high degree of accuracy could potentially use timing differences to gain knowledge of the password. This is [understood to be feasible on a local network, but not on the public internet](https://groups.google.com/d/msg/django-developers/iAaq0pvHXuA/fpUuwjK3i2wJ). Privacy settings that restrict access to pages/documents on a per-user or per-group basis (as opposed to a shared password) are unaffected by this vulnerability. This has been patched in 2.7.3, 2.8.2, 2.9.
Timeline
- CVE published
- Record last updated
Affected versions
- wagtail Wagtail
fixed in 2.7.3; From 2.8rc1 · fixed in 2.8.2
- wagtailPyPI
From 2.7 · fixed in 2.7.3; From 2.8 · fixed in 2.8.2
- wagtailPyPI
fixed in 2.7.3
- wagtailPyPI
From 2.8rc1 · fixed in 2.8.2
- wagtailPyPI
From 2.9rc1 · fixed in 2.9