<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Fri, 09 Oct 2026 19:55:53 +0000</lastBuildDate>
    <item>
      <title>CVE-2020-11037 — Potential Observable Timing Discrepancy in Wagtail</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2020-11037</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Wagtail&lt;/p&gt;
&lt;p&gt;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&amp;#39;s &amp;#34;Privacy&amp;#34; 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).&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;This has been patched in 2.7.3, 2.8.2, 2.9.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Wagtail&lt;/p&gt;
&lt;p&gt;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&amp;#39;s &amp;#34;Privacy&amp;#34; 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).&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;This has been patched in 2.7.3, 2.8.2, 2.9.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2020-11037</guid>
    </item>
    <item>
      <title>GHSA-jjjr-3jcw-f8v6 — Potential Observable Timing Discrepancy in Wagtail</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-jjjr-3jcw-f8v6</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: wagtail&lt;/p&gt;
&lt;p&gt;### Impact
A potential timing attack exists on pages or documents that have been protected with a shared password through Wagtail&amp;#39;s &amp;#34;Privacy&amp;#34; 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).)&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;### Patches
Patched versions have been released as Wagtail 2.7.3 (for the LTS 2.7 branch), Wagtail 2.8.2 and Wagtail 2.9.&lt;/p&gt;
&lt;p&gt;### Workarounds
Site owners who are unable to upgrade to the new versions can use [user- or group-based privacy restrictions](https://docs.wagtail.io/en/stable/advanced_topics/privacy.html) to restrict access to sensitive information; these are unaffected by this vulnerability.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: wagtail&lt;/p&gt;
&lt;p&gt;### Impact
A potential timing attack exists on pages or documents that have been protected with a shared password through Wagtail&amp;#39;s &amp;#34;Privacy&amp;#34; 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).)&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;### Patches
Patched versions have been released as Wagtail 2.7.3 (for the LTS 2.7 branch), Wagtail 2.8.2 and Wagtail 2.9.&lt;/p&gt;
&lt;p&gt;### Workarounds
Site owners who are unable to upgrade to the new versions can use [user- or group-based privacy restrictions](https://docs.wagtail.io/en/stable/advanced_topics/privacy.html) to restrict access to sensitive information; these are unaffected by this vulnerability.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-jjjr-3jcw-f8v6</guid>
    </item>
  </channel>
</rss>
