https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 02 Oct 2026 15:48:55 +0000 https://cve.radiocsirt.org/vuln/euvd-2026-68437 EUVD-2026-68437 https://cve.radiocsirt.org/vuln/euvd-2026-68437 https://cve.radiocsirt.org/vuln/fkie_cve-2018-16984 <p>An issue was discovered in Django 2.1 before 2.1.2, in which unprivileged users can read the password hashes of arbitrary accounts. The read-only password widget used by the Django Admin to display an obfuscated password hash was bypassed if a user has only the &#34;view&#34; permission (new in Django 2.1), resulting in display of the entire password hash to those users. This may result in a vulnerability for sites with legacy user accounts using insecure hashes.</p> <p>An issue was discovered in Django 2.1 before 2.1.2, in which unprivileged users can read the password hashes of arbitrary accounts. The read-only password widget used by the Django Admin to display an obfuscated password hash was bypassed if a user has only the &#34;view&#34; permission (new in Django 2.1), resulting in display of the entire password hash to those users. This may result in a vulnerability for sites with legacy user accounts using insecure hashes.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2018-16984 https://cve.radiocsirt.org/vuln/ghsa-6mx3-3vqg-hpp2 <p><strong>Affected:</strong> PyPI: Django</p> <p>An issue was discovered in Django 2.1 before 2.1.2, in which unprivileged users can read the password hashes of arbitrary accounts. The read-only password widget used by the Django Admin to display an obfuscated password hash was bypassed if a user has only the &#34;view&#34; permission (new in Django 2.1), resulting in display of the entire password hash to those users. This may result in a vulnerability for sites with legacy user accounts using insecure hashes.</p> <p><strong>Affected:</strong> PyPI: Django</p> <p>An issue was discovered in Django 2.1 before 2.1.2, in which unprivileged users can read the password hashes of arbitrary accounts. The read-only password widget used by the Django Admin to display an obfuscated password hash was bypassed if a user has only the &#34;view&#34; permission (new in Django 2.1), resulting in display of the entire password hash to those users. This may result in a vulnerability for sites with legacy user accounts using insecure hashes.</p> https://cve.radiocsirt.org/vuln/ghsa-6mx3-3vqg-hpp2 https://cve.radiocsirt.org/vuln/gsd-2018-16984 gsd-2018-16984 https://cve.radiocsirt.org/vuln/gsd-2018-16984 https://cve.radiocsirt.org/vuln/opensuse-su-2024:11205-1 <p>python36-Django-3.2.7-2.3 on GA media</p> <p>python36-Django-3.2.7-2.3 on GA media</p> https://cve.radiocsirt.org/vuln/opensuse-su-2024:11205-1 https://cve.radiocsirt.org/vuln/pysec-2018-3 <p><strong>Affected:</strong> PyPI: django</p> <p>An issue was discovered in Django 2.1 before 2.1.2, in which unprivileged users can read the password hashes of arbitrary accounts. The read-only password widget used by the Django Admin to display an obfuscated password hash was bypassed if a user has only the &#34;view&#34; permission (new in Django 2.1), resulting in display of the entire password hash to those users. This may result in a vulnerability for sites with legacy user accounts using insecure hashes.</p> <p><strong>Affected:</strong> PyPI: django</p> <p>An issue was discovered in Django 2.1 before 2.1.2, in which unprivileged users can read the password hashes of arbitrary accounts. The read-only password widget used by the Django Admin to display an obfuscated password hash was bypassed if a user has only the &#34;view&#34; permission (new in Django 2.1), resulting in display of the entire password hash to those users. This may result in a vulnerability for sites with legacy user accounts using insecure hashes.</p> https://cve.radiocsirt.org/vuln/pysec-2018-3