{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-17354 exists.","fix":"Upgrade to a fixed version.","what":"CVE-2020-17354 is a high-severity vulnerability in n/a, published on 15 Apr 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2020-17354 and fix it if it is affected.\n\nWhat it is: CVE-2020-17354 is a high-severity vulnerability in n/a, published on 15 Apr 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-17354 exists.\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-2020-17354/ (Markdown: https://insights.sbomify.com/CVE-2020-17354/index.md)","id":"CVE-2020-17354","markdown":"https://insights.sbomify.com/CVE-2020-17354/index.md","name":"CVE-2020-17354","record":{"aliases":["DEBIAN-CVE-2020-17354","GHSA-vm3h-24gm-v3q6","MGASA-2023-0325","UBUNTU-CVE-2020-17354"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["code_execution","security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Music notation software","requires_auth":"none","summary":"Attackers can bypass LilyPond's safe mode protection to execute arbitrary code via malicious input files, requiring an upgrade to a patched version.","user_interaction":"required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"lilypond","vendor":"lilypond"}],"cvss":{"score":8.6,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"}],"description":"LilyPond before 2.24 allows attackers to bypass the -dsafe protection mechanism via output-def-lookup or output-def-scope, as demonstrated by dangerous Scheme code in a .ly file that causes arbitrary code execution during conversion to a different file format. NOTE: in 2.24 and later versions, safe mode is removed, and the product no longer tries to block code execution when external files are used.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Security feature bypass in n/a","id":"CVE-2020-17354","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2020"},"n_packages":0,"n_references":8,"next":{"headline":"Denial of service in n/a","id":"CVE-2020-17355"},"packages":[],"prev":{"headline":"Code injection in n/a","id":"CVE-2020-17353"},"products":["n/a"],"published":"2023-04-15","related":[{"cvss_score":9.8,"headline":"Command injection in n/a","id":"CVE-2018-10992","kev_date_added":null,"published":"2018-05-11"},{"cvss_score":8.8,"headline":"Command injection in n/a","id":"CVE-2017-17523","kev_date_added":null,"published":"2017-12-11"}],"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":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-02-06","vendors":["n/a"]},"summary":"Attackers can bypass LilyPond's safe mode protection to execute arbitrary code via malicious input files, requiring an upgrade to a patched version.","url":"https://insights.sbomify.com/CVE-2020-17354/"}