CVE-2020-17354

What it is

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.

At a glance

Exploitability

Can be exploited locally on the machine without logging in, but needs a user to act. High risk of data exposure, data tampering, service disruption.

Exploit odds

0.4% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2023-04-15 22:15 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-17 02:58 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 0.4% in the next 30 days (EPSS).
• Severity: 8.6 HIGH (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2023-04-15 22:15 UTC

Last modified

2026-06-17 02:58 UTC

Exploit probability

0.4% · EPSS, next 30 days

Weakness

CWE-863 · Incorrect authorization

Record status

Modified

Affected

• Lilypond < 2.24.0

Attack profile CVSS 3.1 · 8.6

Attack vector

Local

Complexity

Low

Privileges needed

None

User interaction

Required

Scope

Changed

Confidentiality

High

Integrity

High

Availability

High

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2020-17354.md and follow it. Check whether this project is affected by CVE-2020-17354. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge