blob: cf9b4807fe7192478e0e657f1c3bdcb46032946c [file] [log] [blame]
<?xml version="1.0" encoding="utf-8"?>
<glsa id="200902-06">
<title>GNU Emacs, XEmacs: Multiple vulnerabilities</title>
Two vulnerabilities were found in GNU Emacs, possibly leading to
user-assisted execution of arbitrary code. One also affects edit-utils in
<product type="ebuild">emacs edit-utils</product>
<announced>February 23, 2009</announced>
<revised>February 23, 2009: 01</revised>
<package name="app-editors/emacs" auto="yes" arch="*">
<unaffected range="ge">22.2-r3</unaffected>
<unaffected range="rge">21.4-r17</unaffected>
<unaffected range="lt">19</unaffected>
<vulnerable range="lt">22.2-r3</vulnerable>
<package name="app-xemacs/edit-utils" auto="yes" arch="*">
<unaffected range="ge">2.39</unaffected>
<vulnerable range="lt">2.39</vulnerable>
GNU Emacs and XEmacs are highly extensible and customizable text
editors. edit-utils are miscellaneous extensions to XEmacs.
Morten Welinder reports about GNU Emacs and edit-utils in XEmacs: By
shipping a .flc accompanying a source file (.c for example) and setting
font-lock-support-mode to fast-lock-mode in the source file through
local variables, any Lisp code in the .flc file is executed without
warning (CVE-2008-2142).
Romain Francoise reported a security risk in a feature of GNU Emacs
related to interacting with Python. The vulnerability arises because
Python, by default, prepends the current directory to the module search
path, allowing for arbitrary code execution when launched from a
specially crafted directory (CVE-2008-3949).
<impact type="normal">
Remote attackers could entice a user to open a specially crafted file
in GNU Emacs, possibly leading to the execution of arbitrary Emacs Lisp
code or arbitrary Python code with the privileges of the user running
GNU Emacs or XEmacs.
There is no known workaround at this time.
All GNU Emacs users should upgrade to the latest version:
# emerge --sync
# emerge --ask --oneshot --verbose &quot;&gt;=app-editors/emacs-22.2-r3&quot;</code>
All edit-utils users should upgrade to the latest version:
# emerge --sync
# emerge --ask --oneshot --verbose &quot;&gt;=app-xemacs/edit-utils-2.39&quot;</code>
<uri link="">CVE-2008-2142</uri>
<uri link="">CVE-2008-3949</uri>
<metadata tag="requester" timestamp="Sun, 06 Jul 2008 22:12:00 +0000">
<metadata tag="bugReady" timestamp="Sat, 12 Jul 2008 19:44:28 +0000">
<metadata tag="submitter" timestamp="Mon, 09 Feb 2009 22:47:35 +0000">