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.

The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - 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.
    (CVE-2020-17354)

Note that Nessus relies on the presence of the package as reported by the vendor.

The remote openSUSE 15 host has packages installed that are affected by multiple vulnerabilities as referenced in the openSUSE-SU-2023:0137-1 advisory.

  - The mkdir procedure of GNU Guile temporarily changed the process' umask to zero. During that time window,     in a multithreaded application, other threads could end up creating files with insecure permissions. For     example, mkdir without the optional mode argument would create directories as 0777. This is fixed in Guile     2.0.13. Prior versions are affected. (CVE-2016-8605)

  - 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.
    (CVE-2020-17354)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote Fedora 36 host has packages installed that are affected by a vulnerability as referenced in the FEDORA-2023-6edb8fab0d advisory.

    Fix for CVE-2020-17354

Tenable has extracted the preceding description block directly from the Fedora security advisory.

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

The remote Fedora 37 host has packages installed that are affected by a vulnerability as referenced in the FEDORA-2023-fb8bc496c2 advisory.

    Fix for CVE-2020-17354

Tenable has extracted the preceding description block directly from the Fedora security advisory.

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

ID	Name	Product	Family	Severity
223426	Linux Distros Unpatched Vulnerability : CVE-2020-17354	Nessus	Misc.	high
177676	openSUSE 15 Security Update : guile1, lilypond (openSUSE-SU-2023:0137-1)	Nessus	SuSE Local Security Checks	high
174767	Fedora 36 : lilypond / lilypond-doc (2023-6edb8fab0d)	Nessus	Fedora Local Security Checks	high
174763	Fedora 37 : lilypond / lilypond-doc (2023-fb8bc496c2)	Nessus	Fedora Local Security Checks	high

Detections

Analytics

CVE-2020-17354

high

Tenable Plugins

high

high

high

high