CVE-2020-17354: High severity lilypond vulnerability

Published Apr 15, 2023
·
Updated

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.

Affected Software

1 affected component
lilypond lilypond<2.24.0

Event History

Apr 15, 2023
CVE Published
via MITRE·12:00 AM
Data Sourced
via MITRE·12:00 AM
Description
Data Sourced
via NVD·10:15 PM
RemedyDescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2020-17354?

CVE-2020-17354 has a high severity level due to the potential for arbitrary code execution.

2

How do I fix CVE-2020-17354?

The recommended fix for CVE-2020-17354 is to upgrade LilyPond to version 2.24.0 or later.

3

What versions of LilyPond are affected by CVE-2020-17354?

CVE-2020-17354 affects all versions of LilyPond prior to 2.24.0.

4

What type of attack does CVE-2020-17354 enable?

CVE-2020-17354 enables attackers to bypass the -dsafe protection mechanism and execute arbitrary code.

5

Is there any known exploit for CVE-2020-17354?

Yes, CVE-2020-17354 is demonstrated by inserting dangerous Scheme code into .ly files during file format conversion.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203