{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2016-1601 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2016-1601 is a critical vulnerability in n/a, published on 26 Apr 2016. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2016-1601 and fix it if it is affected.\n\nWhat it is: CVE-2016-1601 is a critical vulnerability in n/a, published on 26 Apr 2016. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2016-1601 in the wild and no public exploit code.\n\nAffected product: n/a. 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-2016-1601/ (Markdown: https://insights.sbomify.com/CVE-2016-1601/index.md)","id":"CVE-2016-1601","markdown":"https://insights.sbomify.com/CVE-2016-1601/index.md","name":"CVE-2016-1601","record":{"aliases":["GHSA-m3qr-hrgx-v5ph","SUSE-SU-2016:1138-1","openSUSE-SU-2024:10149-1"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["privilege_escalation"],"network_reachable":"yes","non_default_config":true,"product_category":"SUSE Linux Enterprise","requires_auth":"none","summary":"Attackers may gain unauthorized access because AutoYaST installations leave user password fields empty in the shadow file.","user_interaction":"not_required","vuln_class":"misconfiguration"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"microfocus","cpe":[{"product":"yast2","vendor":"suse"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-255","name":null}],"description":"yast2-users before 3.1.47, as used in SUSE Linux Enterprise 12 SP1, does not properly set empty password fields in /etc/shadow during an AutoYaST installation when the profile does not contain inst-sys users, which might allow attackers to have unspecified impact via unknown vectors.","ecosystems":["SUSE:Linux Enterprise Desktop 12 SP1","SUSE:Linux Enterprise Server 12 SP1","SUSE:Linux Enterprise Server for SAP Applications 12 SP1","SUSE:Linux Enterprise Software Development Kit 12 SP1","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":"Misconfiguration in n/a","id":"CVE-2016-1601","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"misconfiguration","year":"2016"},"n_packages":5,"n_references":4,"next":{"headline":"Code injection in supportconfig","id":"CVE-2016-1602"},"packages":[{"ecosystem":"SUSE:Linux Enterprise Desktop 12 SP1","fixed":["3.1.41.3-9.1"],"introduced":["0"],"last_affected":[],"package":"yast2-users","purl":"pkg:rpm/suse/yast2-users\u0026distro=SUSE%20Linux%20Enterprise%20Desktop%2012%20SP1","source":"SUSE-SU-2016:1138-1"},{"ecosystem":"SUSE:Linux Enterprise Server 12 SP1","fixed":["3.1.41.3-9.1"],"introduced":["0"],"last_affected":[],"package":"yast2-users","purl":"pkg:rpm/suse/yast2-users\u0026distro=SUSE%20Linux%20Enterprise%20Server%2012%20SP1","source":"SUSE-SU-2016:1138-1"},{"ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 12 SP1","fixed":["3.1.41.3-9.1"],"introduced":["0"],"last_affected":[],"package":"yast2-users","purl":"pkg:rpm/suse/yast2-users\u0026distro=SUSE%20Linux%20Enterprise%20Server%20for%20SAP%20Applications%2012%20SP1","source":"SUSE-SU-2016:1138-1"},{"ecosystem":"SUSE:Linux Enterprise Software Development Kit 12 SP1","fixed":["3.1.41.3-9.1"],"introduced":["0"],"last_affected":[],"package":"yast2-users","purl":"pkg:rpm/suse/yast2-users\u0026distro=SUSE%20Linux%20Enterprise%20Software%20Development%20Kit%2012%20SP1","source":"SUSE-SU-2016:1138-1"},{"ecosystem":"openSUSE:Tumbleweed","fixed":["3.2.6-1.1"],"introduced":["0"],"last_affected":[],"package":"yast2-users","purl":"pkg:rpm/opensuse/yast2-users\u0026distro=openSUSE%20Tumbleweed","source":"openSUSE-SU-2024:10149-1"}],"prev":{"headline":"Information disclosure in Identity Manager","id":"CVE-2016-1600"},"products":["n/a"],"published":"2016-04-26","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":"SUSE"},{"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-08-05","vendors":["n/a"]},"summary":"Attackers may gain unauthorized access because AutoYaST installations leave user password fields empty in the shadow file.","url":"https://insights.sbomify.com/CVE-2016-1601/"}