Vulnerability in lilypond
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as DEBIAN-CVE-2020-17354 has been found in lilypond.
Successful exploitation can lead to full system takeover.
What to do: upgrade lilypond to 2.22.1-1 or later.
If unsure, ask your IT team or search "lilypond DEBIAN-CVE-2020-17354" on the vendor's site.
DEBIAN-CVE-2020-17354 (lilypond)
Attack vector: local / unauthenticated
Patched: 2.22.1-1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (unclassified) exists in lilypond.
Check the vendor advisory for the affected versions of lilypond.
Severity: ?. Successful exploitation can lead to full system takeover.
Update to 2.22.1-1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'lilypond' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1
Identify exposureidentify
grep -r 'lilypond' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
lilypondを grep し、稼働しているサービス・バージョンを把握する。 -
2
Apply patchpatch
Upgrade lilypond to 2.22.1-1ステージング環境で 2.22.1-1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3
Post-deployment verificationverify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
| Ecosystem | Package | Affected | Fixed |
|---|---|---|---|
| Debian:12 | lilypond |
< 2.22.1-1 |
2.22.1-1 |
| Debian:13 | lilypond |
< 2.22.1-1 |
2.22.1-1 |
| Debian:14 | lilypond |
< 2.22.1-1 |
2.22.1-1 |
Original description The description as published by the source.
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.
Source: OSV.dev (Open Source Vulnerabilities) OSV
References
- advisory security-tracker.debian.org