CVE-2018-10992: Critical severity lilypond lilypond vulnerability
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.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2018-10992?
CVE-2018-10992 is considered a high severity vulnerability due to its potential for remote code execution through argument-injection attacks.
How do I fix CVE-2018-10992?
To fix CVE-2018-10992, upgrade to LilyPond version 2.19.81 or later where the vulnerability has been addressed.
Who is affected by CVE-2018-10992?
Users of LilyPond version 2.19.80 are specifically affected by CVE-2018-10992.
What is the nature of the vulnerability in CVE-2018-10992?
The vulnerability in CVE-2018-10992 arises from insufficient validation of strings before executing the program specified by the BROWSER environment variable.
Can CVE-2018-10992 lead to remote code execution?
Yes, CVE-2018-10992 can lead to remote code execution through crafted URLs that initiate argument-injection attacks.