Описание
lilypond-invoke-editor in LilyPond 2.19.80 does not validate strings before launching the program specified by the BROWSER environment variable, which allows remote attackers to conduct argument-injection attacks via a crafted URL, as demonstrated by a --proxy-pac-file argument, because the GNU Guile code uses the system Scheme procedure instead of the system* Scheme procedure. NOTE: this vulnerability exists because of an incomplete fix for CVE-2017-17523.
| Релиз | Статус | Примечание |
|---|---|---|
| artful | ignored | end of life |
| bionic | ignored | end of standard support, was needed |
| cosmic | not-affected | 2.19.81+really-2.18.2-13 |
| devel | not-affected | 2.19.81+really-2.18.2-13 |
| disco | not-affected | 2.19.81+really-2.18.2-13 |
| eoan | not-affected | 2.19.81+really-2.18.2-13 |
| esm-apps/bionic | needed | |
| esm-apps/focal | not-affected | 2.19.81+really-2.18.2-13 |
| esm-apps/jammy | not-affected | 2.19.81+really-2.18.2-13 |
| esm-apps/noble | not-affected | 2.19.81+really-2.18.2-13 |
Показывать по
EPSS
7.5 High
CVSS2
9.8 Critical
CVSS3
Связанные уязвимости
lilypond-invoke-editor in LilyPond 2.19.80 does not validate strings before launching the program specified by the BROWSER environment variable, which allows remote attackers to conduct argument-injection attacks via a crafted URL, as demonstrated by a --proxy-pac-file argument, because the GNU Guile code uses the system Scheme procedure instead of the system* Scheme procedure. NOTE: this vulnerability exists because of an incomplete fix for CVE-2017-17523.
lilypond-invoke-editor in LilyPond 2.19.80 does not validate strings b ...
lilypond-invoke-editor in LilyPond 2.19.80 does not validate strings before launching the program specified by the BROWSER environment variable, which allows remote attackers to conduct argument-injection attacks via a crafted URL, as demonstrated by a --proxy-pac-file argument, because the GNU Guile code uses the system Scheme procedure instead of the system* Scheme procedure. NOTE: this vulnerability exists because of an incomplete fix for CVE-2017-17523.
EPSS
7.5 High
CVSS2
9.8 Critical
CVSS3