<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-03T10:30:56.458994+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-189464</id>
    <title>EUVD-2026-189464</title>
    <updated>2026-10-03T10:30:56.512329+00:00</updated>
    <content>EUVD-2026-189464</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-189464"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2024-47182</id>
    <title>fkie_cve-2024-47182</title>
    <updated>2026-10-03T10:30:56.512371+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Dozzle is a realtime log viewer for docker containers. Before version 8.5.3, the app uses sha-256 as the hash for passwords, which leaves users susceptible to rainbow table attacks. The app switches to bcrypt, a more appropriate hash for passwords, in version 8.5.3.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2024-47182"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-w7qr-q9fh-fj35</id>
    <title>GHSA-w7qr-q9fh-fj35 — Dozzle uses unsafe hash for passwords</title>
    <updated>2026-10-03T10:30:56.512405+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Go: github.com/amir20/dozzle</p>
<p>### Summary
The app uses sha-256 as the hash for passwords. The app should switch to bcrypt.</p>
<p>### Details
SHA-256 is a message digest hash, and not classified as secure for password hashing. Message digest hashes are designed to be fast, while password hashing mechanisms are designed with certain cryptographic properties (e.g. slow) to protect against vulnerabilities. Refer to the links below for more information:
- https://security.stackexchange.com/questions/195563/why-is-sha-256-not-good-for-passwords
- https://stackoverflow.com/questions/11624372/best-practice-for-hashing-passwords-sha256-or-sha512
- https://cheatsheetseries.owasp.org/cheatsheets/Password_Storage_Cheat_Sheet.html#pre-hashing-passwords-with-bcrypt</p>
<p>### PoC
N/A</p>
<p>### Impact
It leaves users susceptible to rainbow table attacks</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-w7qr-q9fh-fj35"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/opensuse-su-2024:0350-1</id>
    <title>openSUSE-SU-2024:0350-1 — Security update for govulncheck-vulndb</title>
    <updated>2026-10-03T10:30:56.512436+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Security update for govulncheck-vulndb</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/opensuse-su-2024:0350-1"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/suse-su-2024:3911-1</id>
    <title>SUSE-SU-2024:3911-1 — Security update for govulncheck-vulndb</title>
    <updated>2026-10-03T10:30:56.512471+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Security update for govulncheck-vulndb</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/suse-su-2024:3911-1"/>
  </entry>
</feed>
