CVE-2018-20167
Summary
| CVE | CVE-2018-20167 |
|---|---|
| State | PUBLIC |
| Assigner | [email protected] |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2018-12-17 05:29:00 UTC |
| Updated | 2019-10-03 00:03:00 UTC |
| 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. |
Risk And Classification
Problem Types: CWE-74
NVD Known Affected Configurations (CPE 2.3)
| Type | Vendor | Product | Version | Update | Edition | Language |
|---|---|---|---|---|---|---|
| Application | Enlightenment | Terminology | All | All | All | All |
| Application | Enlightenment | Terminology | All | All | All | All |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| ⚓ T7504 media_unknown_handle in \e}pn<FILE>\0 control sequence allows remote code execution (RCE) | MISC | phab.enlightenment.org | Exploit, Mitigation, Vendor Advisory |
| rTRM1ac204da9148 | MISC | phab.enlightenment.org | Mitigation, Patch, Vendor Advisory |
| Terminology 1.3.1 Release | MISC | www.enlightenment.org | Mitigation, Vendor Advisory |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.