Potential Observable Timing Discrepancy in Wagtail
Wagtail
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| wagtail PyPI |
|
|
Wagtail
| Product | Affected | Fixed in |
|---|---|---|
| wagtail PyPI |
|
|
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.
From the CVE record · GitHub_M
Wagtail compares shared passwords for Privacy-protected pages and documents character by character. An attacker who can measure response times accurately could potentially learn the password through timing differences; this is understood to be feasible on a local network, but not on the public internet. Per-user and per-group access controls are unaffected.
Teams running the PyPI wagtail package before 2.7.3, from 2.8rc1 to before 2.8.2, or from 2.9rc1 to before 2.9 should check their installations.