{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-3700 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"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."},"fix_prompt":"Check this codebase for CVE-2019-3700 and fix it if it is affected.\n\nWhat 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.\nExploitation: There is no known exploitation of CVE-2019-3700 in the wild and no public exploit code.\n\nAffected product: openSUSE Factory. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2019-3700/ (Markdown: https://insights.sbomify.com/CVE-2019-3700/index.md)","id":"CVE-2019-3700","markdown":"https://insights.sbomify.com/CVE-2019-3700/index.md","name":"CVE-2019-3700","record":{"aliases":["GHSA-6ff8-jh7v-68j7","openSUSE-SU-2024:11536-1"],"analysis":{"component_type":"operating_system","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"openSUSE security tool","requires_auth":"none","summary":"An attacker with access to password hashes can crack DES-encrypted passwords due to insecure defaults in yast2-security.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"suse","cpe":[{"product":"yast2-security","vendor":"suse"}],"cvss":{"score":2.9,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-327","name":"Use of a Broken or Risky Cryptographic Algorithm"}],"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.","ecosystems":["openSUSE:Tumbleweed"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"yast: Fallback to DES without configuration in /etc/login.def","id":"CVE-2019-3700","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"weak_cryptography","year":"2019"},"n_packages":1,"n_references":1,"next":{"headline":"Memory corruption in n/a","id":"CVE-2019-3701"},"packages":[{"ecosystem":"openSUSE:Tumbleweed","fixed":["4.4.1-1.2"],"introduced":["0"],"last_affected":[],"package":"yast2-security","purl":"pkg:rpm/opensuse/yast2-security\u0026distro=openSUSE%20Tumbleweed","source":"openSUSE-SU-2024:11536-1"}],"prev":{"headline":"Local privilege escalation from user privoxy to root","id":"CVE-2019-3699"},"products":["Factory"],"published":"2020-01-24","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"SUSE","prefix":"openSUSE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-09-17","vendors":["openSUSE"]},"summary":"An attacker with access to password hashes can crack DES-encrypted passwords due to insecure defaults in yast2-security.","url":"https://insights.sbomify.com/CVE-2019-3700/"}