Arbitrary Code Injection Affecting terminology package, versions <1.3.1-1
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-DEBIAN12-TERMINOLOGY-1560553
- published17 Dec 2018
- disclosed17 Dec 2018
Introduced: 17 Dec 2018
CVE-2018-20167 (opens in a new tab)How to fix?
Upgrade Debian:12 terminology to version 1.3.1-1 or higher.
NVD Description
Note: Versions mentioned in the description apply only to the upstream terminology package and not the terminology package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
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.