CVE-2018-20167: High severity enlightenment terminology vulnerability
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 handleunknownmedia() 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.
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2018-20167?
CVE-2018-20167 has a severity rating that allows for remote code execution vulnerabilities in versions of Terminology before 1.3.1.
How do I fix CVE-2018-20167?
To fix CVE-2018-20167, update the Terminology software to version 1.3.1 or later.
What software is affected by CVE-2018-20167?
CVE-2018-20167 affects the Enlightenment Terminology application versions prior to 1.3.1.
What vulnerability does CVE-2018-20167 exploit?
CVE-2018-20167 exploits mishandling of popmedia control sequences that lead to remote code execution.
Can CVE-2018-20167 be exploited remotely?
Yes, CVE-2018-20167 can be exploited remotely, allowing attackers to execute arbitrary commands.