{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-18684 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-18684 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-18684 is a high-severity vulnerability in n/a, published on 4 Nov 2019. 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-18684 and fix it if it is affected.\n\nWhat it is: CVE-2019-18684 is a high-severity vulnerability in n/a, published on 4 Nov 2019. 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-18684 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-18684/ (Markdown: https://insights.sbomify.com/CVE-2019-18684/index.md)","id":"CVE-2019-18684","markdown":"https://insights.sbomify.com/CVE-2019-18684/index.md","name":"CVE-2019-18684","record":{"aliases":["GHSA-h9q8-53pc-hhxf"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Sudo privilege escalation","requires_auth":"low_privilege","summary":"Local attackers can exploit a race condition in Sudo to escalate privileges to root by manipulating file descriptors during password prompts.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"sudo","vendor":"sudo_project"}],"cvss":{"score":7,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-362","name":"Concurrent Execution using Shared Resource with Improper Synchronization"}],"description":"Sudo through 1.8.29 allows local users to escalate to root if they have write access to file descriptor 3 of the sudo process. This occurs because of a race condition between determining a uid, and the setresuid and openat system calls. The attacker can write \"ALL ALL=(ALL) NOPASSWD:ALL\" to /proc/#####/fd/3 at a time when Sudo is prompting for a password. NOTE: This has been disputed due to the way Linux /proc works. It has been argued that writing to /proc/#####/fd/3 would only be viable if you had permission to write to /etc/sudoers. Even with write permission to /proc/#####/fd/3, it would not help you write to /etc/sudoers","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Race condition in n/a","id":"CVE-2019-18684","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"race_condition","year":"2019"},"n_packages":0,"n_references":1,"next":{"headline":"DO NOT USE THIS CANDIDATE NUMBER.","id":"CVE-2019-18685"},"packages":[],"prev":{"headline":"Use after free in n/a","id":"CVE-2019-18683"},"products":["n/a"],"published":"2019-11-04","related":[{"cvss_score":8.2,"headline":"Command injection in n/a","id":"CVE-2017-1000368","kev_date_added":null,"published":"2017-06-05"},{"cvss_score":7.2,"headline":"Privilege escalation in n/a","id":"CVE-2015-5602","kev_date_added":null,"published":"2015-11-17"},{"cvss_score":7.1,"headline":"Memory corruption in n/a","id":"CVE-2022-43995","kev_date_added":null,"published":"2022-11-02"},{"cvss_score":7,"headline":"Privilege escalation in n/a","id":"CVE-2023-42465","kev_date_added":null,"published":"2023-12-22"},{"cvss_score":7,"headline":"Race condition in n/a","id":"CVE-2015-8239","kev_date_added":null,"published":"2017-10-10"},{"cvss_score":6.6,"headline":"Sudo: improper handling of ipa_hostname leads to privilege mismanagement","id":"CVE-2023-7090","kev_date_added":null,"published":"2023-12-23"}],"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":"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":"Local attackers can exploit a race condition in Sudo to escalate privileges to root by manipulating file descriptors during password prompts.","url":"https://insights.sbomify.com/CVE-2019-18684/"}