CVE-2020-17354

HIGHNVD 8.68.6—
EchelonGraph scoreMEDIUM confidence

Score 8.6 from GitHub Security Advisory (severity: HIGH) published 2023-04-16. NVD baseline CVSS 8.6; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Elevated
8.6EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 8.6Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
8.6
EG Score
8.6HIGHmedium confidence
EG Risk
55
EG Risk 55/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity86% × 45%
The EG Score, 8.6 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.4%
EPSS %ILE
33rd
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

Published

April 15, 2023

Last Modified

February 6, 2025

Advisory Details (8)

Auto-updated Sep 1, 2026
Patch available.
Web page

Remove safe mode (!1522) · Merge requests · LilyPond / LilyPond · GitLab

https://gitlab.com/lilypond/lilypond/-/merge_requests/1522
Web page

LilyPond Application Usage: 1.2 Command-line usage

http://lilypond.org/doc/v2.18/Documentation/usage/command_002dline-usage
Web page

Extension:Score/2021 security advisory - MediaWiki

https://www.mediawiki.org/wiki/Extension:Score/2021_security_advisory
Web page

Debian Package Tracker

https://tracker.debian.org/news/1249694/accepted-lilypond-2221-1-source-into-unstable/
Web page

⚓ T259210 LilyPond safe mode escape due to output-def-lookup and output-def-scope (CVE-2020-17354)

https://phabricator.wikimedia.org/T259210
Web page

[SECURITY] Fedora 37 Update: lilypond-doc-2.24.1-1.fc37 - package-announce - Fedora mailing-lists

https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/ST5BLLQ4GDME3SN7UE5OMNE5GZE66X4Y/
Web page

[SECURITY] Fedora 36 Update: lilypond-doc-2.24.1-1.fc36 - package-announce - Fedora mailing-lists

https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/K43PF6VGFJNNGAPY57BW3VMEFFOSMRLF/
Web page

Download (LilyPond – Music notation for everyone)

https://lilypond.org/download.html

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
lilypond2.22.0-10 ... 2.24.4-6 (20 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
lilypond—
  • every version up to 2.22.1-1: fixed in 2.22.1-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
lilypond—
  • every version up to 2.22.1-1: fixed in 2.22.1-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
lilypond—
  • every version up to 2.22.1-1: fixed in 2.22.1-1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 26× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 89 of 164 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 11 repeat rows among the latest 100 are merged into the row they repeat. The 75 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-11 13:43 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  2. 2026-10-10 19:56 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  3. 2026-10-09 20:04 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  4. 2026-10-08 16:38 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  5. 2026-10-07 23:44 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  6. 2026-10-06 15:13 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  7. 2026-10-05 17:39 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  8. 2026-10-04 23:18 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  9. 2026-10-03 14:22 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  10. 2026-10-02 16:22 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  11. 2026-09-30 15:13 UTCEG score recompute
  12. 2026-09-30 14:59 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  13. 2026-09-27 13:40 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  14. 2026-09-26 15:54 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  15. 2026-09-26 00:20 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  16. 2026-09-24 14:00 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  17. 2026-09-23 15:04 UTCOSV refresh
  18. 2026-09-22 14:43 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  19. 2026-09-21 20:28 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  20. 2026-09-20 20:11 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  21. 2026-09-18 19:23 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  22. 2026-09-17 19:22 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  23. 2026-09-16 14:04 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  24. 2026-09-15 03:06 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  25. 2026-09-13 16:42 UTCEPSS rescoreEPSS 0.4% · 34th percentile
Show 64 more
  1. 2026-09-12 14:56 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  2. 2026-09-11 14:48 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  3. 2026-09-11 09:32 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  4. 2026-09-10 09:29 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  5. 2026-09-08 21:56 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  6. 2026-09-07 15:57 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  7. 2026-09-06 13:44 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  8. 2026-09-05 15:24 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  9. 2026-09-04 13:57 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  10. 2026-09-04 09:46 UTCOSV refresh
  11. 2026-09-04 05:03 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  12. 2026-09-02 14:08 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  13. 2026-09-01 03:32 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  14. 2026-08-30 19:14 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  15. 2026-08-30 01:18 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  16. 2026-08-27 14:21 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  17. 2026-08-26 14:42 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  18. 2026-08-25 13:45 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  19. 2026-08-21 23:45 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  20. 2026-08-20 22:52 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  21. 2026-08-19 17:00 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  22. 2026-08-18 13:44 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  23. 2026-08-17 20:29 UTCOSV refresh
  24. 2026-08-17 13:43 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  25. 2026-08-16 14:52 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  26. 2026-08-16 02:11 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  27. 2026-08-15 01:26 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  28. 2026-08-13 21:57 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  29. 2026-08-12 13:47 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  30. 2026-08-09 13:43 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  31. 2026-08-08 16:33 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  32. 2026-08-07 16:23 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  33. 2026-08-06 13:43 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  34. 2026-08-05 19:14 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  35. 2026-08-04 15:06 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  36. 2026-08-04 10:34 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  37. 2026-08-03 10:32 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  38. 2026-08-02 15:57 UTCOSV refresh
  39. 2026-08-02 02:23 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  40. 2026-08-01 04:12 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  41. 2026-07-30 16:25 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  42. 2026-07-30 01:27 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  43. 2026-07-28 15:32 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  44. 2026-07-27 14:06 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  45. 2026-07-26 14:51 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  46. 2026-07-25 14:14 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  47. 2026-07-24 14:14 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  48. 2026-07-23 14:15 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  49. 2026-07-23 01:50 UTCEG score recompute
  50. 2026-07-22 22:35 UTCEG score recompute
  51. 2026-07-22 14:05 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  52. 2026-07-21 15:22 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  53. 2026-07-20 17:04 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  54. 2026-07-19 02:26 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  55. 2026-07-18 10:02 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  56. 2026-07-16 16:59 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  57. 2026-07-15 23:23 UTCOSV refresh
  58. 2026-07-15 16:55 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  59. 2026-07-15 01:57 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  60. 2026-07-13 22:27 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  61. 2026-07-13 06:10 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  62. 2026-07-12 05:44 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  63. 2026-07-11 08:25 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  64. 2026-07-09 19:07 UTCEPSS rescoreEPSS 0.4% · 33rd percentile

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2020-17354?
CVE-2020-17354 is a high-severity vulnerability; its CVE record was published on April 15, 2023. 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…
When was the CVE record for CVE-2020-17354 published?
The CVE record for CVE-2020-17354 was published on April 15, 2023. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of February 6, 2025; the record at its source may have been updated since.
Is CVE-2020-17354 actively exploited?
CVE-2020-17354 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (33rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2020-17354?
CVE-2020-17354 has a CVSS v3 base score of 8.6 (NVD).
How do I remediate CVE-2020-17354?
A fix for CVE-2020-17354 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2020-17354

Explore →

Is Your Infrastructure Affected by CVE-2020-17354?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs