CVE-2018-20167
Last modified
CVE-2018-20167 is a vulnerability of currently unknown severity. Terminology before 1.3.1 allows Remote Code Execution because popmedia is mishandled, as demonstrated by an unsafe "cat README.md" command when \e}pn is used. A popmedia control sequence can allow the malicious execution of executable file formats registered in the X desktop share MIME types (/usr/share/applications). EPSS estimates a 2.65% chance of exploitation in the next 30 days.
Description
Terminology before 1.3.1 allows Remote Code Execution because popmedia is mishandled, as demonstrated by an unsafe "cat README.md" command when \e}pn is used. A popmedia control sequence can allow the malicious execution of executable file formats registered in the X desktop share MIME types (/usr/share/applications). The control sequence defers unknown file types to the handle_unknown_media() function, which executes xdg-open against the filename specified in the sequence. The use of xdg-open for all unknown file types allows executable file formats with a registered shared MIME type to be executed. An attacker can achieve remote code execution by introducing an executable file and a plain text file containing the control sequence through a fake software project (e.g., in Git or a tarball). When the control sequence is rendered (such as with cat), the executable file will be run.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Enlightenment | Terminology | < 1.3.1 |
References
- https://phab.enlightenment.org/T7504Exploit, Mitigation, Vendor Advisory
- https://phab.enlightenment.org/rTRM1ac204da9148e7bccb1b5f34b523e2094dfc39e2Mitigation, Patch, Vendor Advisory
- https://www.enlightenment.org/news/2018-12-16-terminology-1.3.1Mitigation, Vendor Advisory
- https://phab.enlightenment.org/T7504Exploit, Mitigation, Vendor Advisory
- https://phab.enlightenment.org/rTRM1ac204da9148e7bccb1b5f34b523e2094dfc39e2Mitigation, Patch, Vendor Advisory
- https://www.enlightenment.org/news/2018-12-16-terminology-1.3.1Mitigation, Vendor Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2018-20167?
How severe is CVE-2018-20167?
How do I fix CVE-2018-20167?
Are you affected by CVE-2018-20167?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
