# CVE-2019-3700: yast: Fallback to DES without configuration in /etc/login.def

> An attacker with access to password hashes can crack DES-encrypted passwords due to insecure defaults in yast2-security.

- **Severity:** Low 2.9 (`CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Jan 2020
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-6ff8-jh7v-68j7, openSUSE-SU-2024:11536-1

## What is CVE-2019-3700?

CVE-2019-3700 is a low-severity vulnerability in openSUSE Factory, published on 24 Jan 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

Weakness: CWE-327 (Use of a Broken or Risky Cryptographic Algorithm)

## Which versions are affected by CVE-2019-3700?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `yast2-security` | openSUSE:Tumbleweed | All versions | 4.4.1-1.2 |

Products: Suse Yast2-Security.

## How do I fix CVE-2019-3700?

Upgrade to a fixed version.

## Is CVE-2019-3700 being exploited?

There is no known exploitation of CVE-2019-3700 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-3700 and fix it if it is affected.

What it is: CVE-2019-3700 is a low-severity vulnerability in openSUSE Factory, published on 24 Jan 2020. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-3700 in the wild and no public exploit code.

Affected product: openSUSE Factory. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2019-3700/ (Markdown: https://insights.sbomify.com/CVE-2019-3700/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2019-3700
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-3700
- OSV: https://osv.dev/vulnerability/CVE-2019-3700

---
From sbomify Insights: https://insights.sbomify.com/CVE-2019-3700/
Summaries are generated and may contain mistakes; the official description above is the record.