https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 09 Oct 2026 18:15:25 +0000 https://cve.radiocsirt.org/vuln/euvd-2026-179981 EUVD-2026-179981 https://cve.radiocsirt.org/vuln/euvd-2026-179981 https://cve.radiocsirt.org/vuln/fkie_cve-2019-3700 <p>yast2-security didn&#39;t use secure defaults to protect passwords. This became a problem on 2019-10-07 when configuration files that set secure settings were moved to a different location. As of the 20191022 snapshot the insecure default settings were used until yast2-security switched to stronger defaults in 4.2.6 and used the new configuration file locations. Password created during this time used DES password encryption and are not properly protected against attackers that are able to access the password hashes.</p> <p>yast2-security didn&#39;t use secure defaults to protect passwords. This became a problem on 2019-10-07 when configuration files that set secure settings were moved to a different location. As of the 20191022 snapshot the insecure default settings were used until yast2-security switched to stronger defaults in 4.2.6 and used the new configuration file locations. Password created during this time used DES password encryption and are not properly protected against attackers that are able to access the password hashes.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2019-3700 https://cve.radiocsirt.org/vuln/ghsa-6ff8-jh7v-68j7 <p>yast2-security didn&#39;t use secure defaults to protect passwords. This became a problem on 2019-10-07 when configuration files that set secure settings were moved to a different location. As of the 20191022 snapshot the insecure default settings were used until yast2-security switched to stronger defaults in 4.2.6 and used the new configuration file locations. Password created during this time used DES password encryption and are not properly protected against attackers that are able to access the password hashes.</p> <p>yast2-security didn&#39;t use secure defaults to protect passwords. This became a problem on 2019-10-07 when configuration files that set secure settings were moved to a different location. As of the 20191022 snapshot the insecure default settings were used until yast2-security switched to stronger defaults in 4.2.6 and used the new configuration file locations. Password created during this time used DES password encryption and are not properly protected against attackers that are able to access the password hashes.</p> https://cve.radiocsirt.org/vuln/ghsa-6ff8-jh7v-68j7 https://cve.radiocsirt.org/vuln/gsd-2019-3700 gsd-2019-3700 https://cve.radiocsirt.org/vuln/gsd-2019-3700 https://cve.radiocsirt.org/vuln/opensuse-su-2024:11536-1 <p>yast2-security-4.4.1-1.2 on GA media</p> <p>yast2-security-4.4.1-1.2 on GA media</p> https://cve.radiocsirt.org/vuln/opensuse-su-2024:11536-1