{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-19234 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2019-19234 is a high-severity authentication bypass vulnerability in n/a, published on 19 Dec 2019. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-19234 and fix it if it is affected.\n\nWhat it is: CVE-2019-19234 is a high-severity authentication bypass vulnerability in n/a, published on 19 Dec 2019. 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-2019-19234 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-2019-19234/ (Markdown: https://insights.sbomify.com/CVE-2019-19234/index.md)","id":"CVE-2019-19234","markdown":"https://insights.sbomify.com/CVE-2019-19234/index.md","name":"CVE-2019-19234","record":{"aliases":["DEBIAN-CVE-2019-19234","GHSA-vh47-792w-24m4","UBUNTU-CVE-2019-19234"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["privilege_escalation","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Sudo privilege tool","requires_auth":"none","summary":"Attackers with sudo access can impersonate users blocked by password hashes, bypassing intended authentication restrictions.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"sudo","vendor":"sudo"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[],"description":"In Sudo through 1.8.29, the fact that a user has been blocked (e.g., by using the ! character in the shadow file instead of a password hash) is not considered, allowing an attacker (who has access to a Runas ALL sudoer account) to impersonate any blocked user. NOTE: The software maintainer believes that this CVE is not valid. Disabling local password authentication for a user is not the same as disabling all access to that user--the user may still be able to login via other means (ssh key, kerberos, etc). Both the Linux shadow(5) and passwd(1) manuals are clear on this. Indeed it is a valid use case to have local accounts that are _only_ accessible via sudo and that cannot be logged into with a password. Sudo 1.8.30 added an optional setting to check the _shell_ of the target user (not the encrypted password!) against the contents of /etc/shells but that is not the same thing as preventing access to users with an invalid password hash","ecosystems":[],"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":"Auth bypass in n/a","id":"CVE-2019-19234","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2019"},"n_packages":0,"n_references":19,"next":{"headline":"Code injection in n/a","id":"CVE-2019-19235"},"packages":[],"prev":{"headline":"Privilege escalation in n/a","id":"CVE-2019-19232"},"products":["n/a"],"published":"2019-12-19","related":[{"cvss_score":7.5,"headline":"Privilege escalation in n/a","id":"CVE-2019-19232","kev_date_added":null,"published":"2019-12-19"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"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 with sudo access can impersonate users blocked by password hashes, bypassing intended authentication restrictions.","url":"https://insights.sbomify.com/CVE-2019-19234/"}