{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-10992 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2018-10992 is a critical command injection vulnerability in n/a, published on 11 May 2018. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-10992 and fix it if it is affected.\n\nWhat it is: CVE-2018-10992 is a critical command injection vulnerability in n/a, published on 11 May 2018. 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-2018-10992 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-2018-10992/ (Markdown: https://insights.sbomify.com/CVE-2018-10992/index.md)","id":"CVE-2018-10992","markdown":"https://insights.sbomify.com/CVE-2018-10992/index.md","name":"CVE-2018-10992","record":{"aliases":["DEBIAN-CVE-2018-10992","GHSA-62j8-9w4c-7rfw","UBUNTU-CVE-2018-10992"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"LilyPond music engraver","requires_auth":"none","summary":"Remote attackers can execute arbitrary commands via argument injection in LilyPond's editor invocation due to improper input validation.","user_interaction":"not_required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"lilypond","vendor":"lilypond"}],"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-88","name":"Improper Neutralization of Argument Delimiters in a Command"}],"description":"lilypond-invoke-editor in LilyPond 2.19.80 does not validate strings before launching the program specified by the BROWSER environment variable, which allows remote attackers to conduct argument-injection attacks via a crafted URL, as demonstrated by a --proxy-pac-file argument, because the GNU Guile code uses the system Scheme procedure instead of the system* Scheme procedure. NOTE: this vulnerability exists because of an incomplete fix for CVE-2017-17523.","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":"Command injection in n/a","id":"CVE-2018-10992","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"command_injection","year":"2018"},"n_packages":0,"n_references":1,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2018-10994"},"packages":[],"prev":{"headline":"Security feature bypass in n/a","id":"CVE-2018-10990"},"products":["n/a"],"published":"2018-05-11","related":[{"cvss_score":8.8,"headline":"Command injection in n/a","id":"CVE-2017-17523","kev_date_added":null,"published":"2017-12-11"},{"cvss_score":8.6,"headline":"Security feature bypass in n/a","id":"CVE-2020-17354","kev_date_added":null,"published":"2023-04-15"}],"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":"Remote attackers can execute arbitrary commands via argument injection in LilyPond's editor invocation due to improper input validation.","url":"https://insights.sbomify.com/CVE-2018-10992/"}