https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sun, 04 Oct 2026 23:46:50 +0000 https://cve.radiocsirt.org/vuln/cnvd-2018-25745 cnvd-2018-25745 https://cve.radiocsirt.org/vuln/cnvd-2018-25745 https://cve.radiocsirt.org/vuln/euvd-2026-70155 EUVD-2026-70155 https://cve.radiocsirt.org/vuln/euvd-2026-70155 https://cve.radiocsirt.org/vuln/fkie_cve-2018-20167 <p>Terminology before 1.3.1 allows Remote Code Execution because popmedia is mishandled, as demonstrated by an unsafe &#34;cat README.md&#34; 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.</p> <p>Terminology before 1.3.1 allows Remote Code Execution because popmedia is mishandled, as demonstrated by an unsafe &#34;cat README.md&#34; 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.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2018-20167 https://cve.radiocsirt.org/vuln/ghsa-mcg2-gcq9-c6xf <p>Terminology before 1.3.1 allows Remote Code Execution because popmedia is mishandled, as demonstrated by an unsafe &#34;cat README.md&#34; 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.</p> <p>Terminology before 1.3.1 allows Remote Code Execution because popmedia is mishandled, as demonstrated by an unsafe &#34;cat README.md&#34; 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.</p> https://cve.radiocsirt.org/vuln/ghsa-mcg2-gcq9-c6xf https://cve.radiocsirt.org/vuln/gsd-2018-20167 gsd-2018-20167 https://cve.radiocsirt.org/vuln/gsd-2018-20167 https://cve.radiocsirt.org/vuln/ubuntu-cve-2018-20167 <p><strong>Affected:</strong> Ubuntu:16.04:LTS: terminology, Ubuntu:18.04:LTS: terminology, Ubuntu:20.04:LTS: terminology, Ubuntu:22.04:LTS: terminology</p> <p>Terminology before 1.3.1 allows Remote Code Execution because popmedia is mishandled, as demonstrated by an unsafe &#34;cat README.md&#34; 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.</p> <p><strong>Affected:</strong> Ubuntu:16.04:LTS: terminology, Ubuntu:18.04:LTS: terminology, Ubuntu:20.04:LTS: terminology, Ubuntu:22.04:LTS: terminology</p> <p>Terminology before 1.3.1 allows Remote Code Execution because popmedia is mishandled, as demonstrated by an unsafe &#34;cat README.md&#34; 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.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2018-20167