# CVE-2020-17354: Security feature bypass in n/a

> Attackers can bypass LilyPond's safe mode protection to execute arbitrary code via malicious input files, requiring an upgrade to a patched version.

- **Severity:** High 8.6 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 15 Apr 2023
- **Updated:** 6 Feb 2025
- **Also known as:** DEBIAN-CVE-2020-17354, GHSA-vm3h-24gm-v3q6, MGASA-2023-0325, UBUNTU-CVE-2020-17354

## What is CVE-2020-17354?

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.

### Official 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.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2020-17354?

It affects 1 product.


Products: Lilypond Lilypond.

## How do I fix CVE-2020-17354?

Upgrade to a fixed version.

## Is CVE-2020-17354 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-17354 exists.

## Other vulnerabilities in n/a

- [CVE-2018-10992](https://insights.sbomify.com/CVE-2018-10992/): Command injection in n/a (critical 9.8)
- [CVE-2017-17523](https://insights.sbomify.com/CVE-2017-17523/): Command injection in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-17354 and fix it if it is affected.

What 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.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-17354 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-17354/ (Markdown: https://insights.sbomify.com/CVE-2020-17354/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-17354
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-17354
- OSV: https://osv.dev/vulnerability/CVE-2020-17354

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-17354/
Summaries are generated and may contain mistakes; the official description above is the record.