2.9
Faible
CVE-2019-3700 yast2-security didn't use secure defaults to protect passwords
Description
yast2-security didn'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.
Produits et versions touchés
| Produit | Versions touchées | Corrigé en |
|---|---|---|
| Factory 4.2 | premières → < 4.2.6 | 4.2.6 |
Références
- bugzilla.suse.com bugzilla.suse.com
Chronologie
- Publiée
- Dernière modification
Autres CVE de Factory
Les 24 CVE de Factory →
CVE-2022-31253
A Untrusted Search Path vulnerability in openldap2 of openSUSE Factory allows local attackers with control of the ldap…
7.1
Élevée
CVE-2022-21946
A Incorrect Permission Assignment for Critical Resource vulnerability in the sudoers configuration in cscreen of…
5.3
Moyenne
CVE-2022-21945
A Insecure Temporary File vulnerability in cscreen of openSUSE Factory allows local attackers to cause DoS for cscreen…
5.1
Moyenne
CVE-2022-21944
A UNIX Symbolic Link (Symlink) Following vulnerability in the systemd service file for watchman of openSUSE Backports…
7.8
Élevée