CVE-2020-17354 · cross-distro fix matrix

CVE-2020-17354: 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

Affects 2 Linux releases across 2 (distro × package) combinations.

Fix per ecosystem

Each block below is a distro release where CVE-2020-17354 has a known fix. Run the listed command on that distro to remediate.

Debian bookworm

Source: Debian Security Tracker

lilypond→ fixed in2.22.1-1urgency: not yet assigned
```
sudo apt-get install --only-upgrade -y lilypond
```

Debian trixie

Source: Debian Security Tracker

lilypond→ fixed in2.22.1-1urgency: not yet assigned
```
sudo apt-get install --only-upgrade -y lilypond
```

Are YOU affected by CVE-2020-17354?

5-second check on your actual server. Reads /etc/os-release, uname -r, and the distro's package manager; matches against this same cross-source index live.

curl https://mindsparkstack.com/scan.sh | bash

Form-based quickscan View on NVD

Continuous monitoring beats manual checking

CVE-2020-17354dropped silently in your distro's update channel. Every new CVE is the same story. StackPatch runs the matcher hourly against all 5 sources and emails the exact remediation when something new applies to one of your servers. $99 lifetime, 50 founder seats, 30-day refund.

See StackPatch ($99 lifetime)