https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sun, 04 Oct 2026 09:22:44 +0000 https://cve.radiocsirt.org/vuln/cleanstart-2025-dr78602 <p><strong>Affected:</strong> CleanStart: harbor-fips</p> <p>Security vulnerability affects the harbor-fips package. This issue is resolved in later releases. See references for vulnerability details.</p> <p><strong>Affected:</strong> CleanStart: harbor-fips</p> <p>Security vulnerability affects the harbor-fips package. This issue is resolved in later releases. See references for vulnerability details.</p> https://cve.radiocsirt.org/vuln/cleanstart-2025-dr78602 https://cve.radiocsirt.org/vuln/euvd-2026-207093 EUVD-2026-207093 https://cve.radiocsirt.org/vuln/euvd-2026-207093 https://cve.radiocsirt.org/vuln/fkie_cve-2024-55885 <p>beego is an open-source web framework for the Go programming language. Versions of beego prior to 2.3.4 use MD5 as a hashing algorithm. MD5 is no longer considered secure against well-funded opponents due to its vulnerability to collision attacks. Version 2.3.4 replaces MD5 with SHA256.</p> <p>beego is an open-source web framework for the Go programming language. Versions of beego prior to 2.3.4 use MD5 as a hashing algorithm. MD5 is no longer considered secure against well-funded opponents due to its vulnerability to collision attacks. Version 2.3.4 replaces MD5 with SHA256.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2024-55885 https://cve.radiocsirt.org/vuln/ghsa-9j3m-fr7q-jxfw <p><strong>Affected:</strong> Go: github.com/beego/beego, Go: github.com/beego/beego/v2</p> <p>In the context of using MD5 to generate filenames for cache keys, there are significant collision hazards that need to be considered. MD5, or Message Digest Algorithm 5, is a widely known cryptographic hash function that produces a 128-bit hash value. However, MD5 is no longer considered secure against well-funded opponents due to its vulnerability to collision attacks.</p> <p>### Understanding Collisions A collision in hashing occurs when two different inputs produce the same hash output. For MD5, this means that it is theoretically possible, and even practical, to find two distinct cache keys that result in the same MD5 hash. This vulnerability has been well-documented and exploited in various security contexts.</p> <p>### Implications for Cache Systems In a cache system where filenames are derived from the MD5 hash of cache keys, a collision could lead to several critical issues:</p> <p>Data Integrity Risks: If two different keys collide, they will map to the same filename. This could result in data being overwritten incorrectly, leading to data loss or corruption. Security Vulnerabilities: An attacker could potentially exploit collisions to manipulate cache data. For instance, by crafting a key that collides with another key, an attacker might gain unauthorized access to sensitive cached information or inject malicious data.</p> <p>Unpredictable Behavior: Collisions can cause the cache system to behave unpredictably, as it may retrieve or store data in unintended files, leading to system instab…</p> <p><strong>Affected:</strong> Go: github.com/beego/beego, Go: github.com/beego/beego/v2</p> <p>In the context of using MD5 to generate filenames for cache keys, there are significant collision hazards that need to be considered. MD5, or Message Digest Algorithm 5, is a widely known cryptographic hash function that produces a 128-bit hash value. However, MD5 is no longer considered secure against well-funded opponents due to its vulnerability to collision attacks.</p> <p>### Understanding Collisions A collision in hashing occurs when two different inputs produce the same hash output. For MD5, this means that it is theoretically possible, and even practical, to find two distinct cache keys that result in the same MD5 hash. This vulnerability has been well-documented and exploited in various security contexts.</p> <p>### Implications for Cache Systems In a cache system where filenames are derived from the MD5 hash of cache keys, a collision could lead to several critical issues:</p> <p>Data Integrity Risks: If two different keys collide, they will map to the same filename. This could result in data being overwritten incorrectly, leading to data loss or corruption. Security Vulnerabilities: An attacker could potentially exploit collisions to manipulate cache data. For instance, by crafting a key that collides with another key, an attacker might gain unauthorized access to sensitive cached information or inject malicious data.</p> <p>Unpredictable Behavior: Collisions can cause the cache system to behave unpredictably, as it may retrieve or store data in unintended files, leading to system instab…</p> https://cve.radiocsirt.org/vuln/ghsa-9j3m-fr7q-jxfw https://cve.radiocsirt.org/vuln/opensuse-su-2024:14603-1 <p>govulncheck-vulndb-0.0.20241218T202206-1.1 on GA media</p> <p>govulncheck-vulndb-0.0.20241218T202206-1.1 on GA media</p> https://cve.radiocsirt.org/vuln/opensuse-su-2024:14603-1