Yast2 Security
Approved changes feed: RSS · Atom
cpe:2.3:a:suse:yast2-security:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Suse (ec535637-432e-5a38-96dd-4ec1e0138f73) |
|---|---|
| Product | Yast2 Security (5a9949e6-7475-527c-9fe4-32431745900b) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from purl2cpe mapping |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/yast/yast-yast2 |
purl2cpe | 2026-06-01 10:12:20.466837 |
pkg:rpm/opensuse/yast2 |
purl2cpe | 2026-06-01 10:12:20.466841 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2019-3700 |
vulnerable | 2026-06-08 05:13:55.384168 |
yast: Fallback to DES without configuration in /etc/login.def
LOW (2.9)
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.
Published: 2020-01-24T12:45:14.347Z
Updated: 2024-09-17T01:26:30.443Z Reference links |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.