LilyPond up to 2.19.80 lilypond-invoke-editor --proxy-pac-file injection
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.4 | $0-$5k | 0.00 |
Summary
A vulnerability categorized as critical has been discovered in LilyPond up to 2.19.80. The affected element is an unknown function of the component lilypond-invoke-editor. Such manipulation of the argument --proxy-pac-file as part of Environment Variable leads to injection. This vulnerability is listed as CVE-2017-17523. The attack may be performed from remote. There is no available exploit. It is advisable to upgrade the affected component.
Details
A vulnerability, which was classified as critical, has been found in LilyPond up to 2.19.80. Affected by this issue is an unknown functionality of the component lilypond-invoke-editor. The manipulation of the argument --proxy-pac-file as part of a Environment Variable leads to a injection vulnerability. Using CWE to declare the problem leads to CWE-74. The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component. Impacted is confidentiality, integrity, and availability. CVE summarizes:
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.
The bug was discovered 11/14/2017. The weakness was presented 12/11/2017 (Website). The advisory is shared for download at bugs.debian.org. This vulnerability is handled as CVE-2017-17523 since 12/11/2017. The attack may be launched remotely. No form of authentication is required for exploitation. Successful exploitation requires user interaction by the victim. There are known technical details, but no exploit is available. The MITRE ATT&CK project declares the attack technique as T1055.
The vulnerability was handled as a non-public zero-day exploit for at least 27 days. During that time the estimated underground price was around $0-$5k.
Upgrading to version 2.19.80 eliminates this vulnerability.
Once again VulDB remains the best source for vulnerability data.
Product
Name
Version
- 2.19.0
- 2.19.1
- 2.19.2
- 2.19.3
- 2.19.4
- 2.19.5
- 2.19.6
- 2.19.7
- 2.19.8
- 2.19.9
- 2.19.10
- 2.19.11
- 2.19.12
- 2.19.13
- 2.19.14
- 2.19.15
- 2.19.16
- 2.19.17
- 2.19.18
- 2.19.19
- 2.19.20
- 2.19.21
- 2.19.22
- 2.19.23
- 2.19.24
- 2.19.25
- 2.19.26
- 2.19.27
- 2.19.28
- 2.19.29
- 2.19.30
- 2.19.31
- 2.19.32
- 2.19.33
- 2.19.34
- 2.19.35
- 2.19.36
- 2.19.37
- 2.19.38
- 2.19.39
- 2.19.40
- 2.19.41
- 2.19.42
- 2.19.43
- 2.19.44
- 2.19.45
- 2.19.46
- 2.19.47
- 2.19.48
- 2.19.49
- 2.19.50
- 2.19.51
- 2.19.52
- 2.19.53
- 2.19.54
- 2.19.55
- 2.19.56
- 2.19.57
- 2.19.58
- 2.19.59
- 2.19.60
- 2.19.61
- 2.19.62
- 2.19.63
- 2.19.64
- 2.19.65
- 2.19.66
- 2.19.67
- 2.19.68
- 2.19.69
- 2.19.70
- 2.19.71
- 2.19.72
- 2.19.73
- 2.19.74
- 2.19.75
- 2.19.76
- 2.19.77
- 2.19.78
- 2.19.79
- 2.19.80
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.6VulDB Meta Temp Score: 7.4
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 8.8
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: InjectionCWE: CWE-74 / CWE-707 / CWE-20
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: LilyPond 2.19.80
Timeline
11/14/2017 🔍12/11/2017 🔍
12/11/2017 🔍
12/11/2017 🔍
12/11/2017 🔍
01/17/2023 🔍
Sources
Advisory: 5243Status: Not defined
CVE: CVE-2017-17523 (🔍)
GCVE (CVE): GCVE-0-2017-17523
GCVE (VulDB): GCVE-100-110468
Entry
Created: 12/11/2017 15:34Updated: 01/17/2023 12:48
Changes: 12/11/2017 15:34 (59), 12/13/2019 16:33 (1), 01/17/2023 12:48 (4)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.