| VuXML ID | Description |
| 66657bd5-ac92-11dd-b541-001f3b19d541 | emacs -- run-python vulnerability
Emacs developers report:
The Emacs command `run-python' launches an interactive
Python interpreter. After the Python process starts up,
Emacs automatically sends it the line:
import emacs
which normally imports a script named emacs.py which is
distributed with Emacs. This script, which is typically
located in a write-protected installation directory with
other Emacs program files, defines various functions to help
the Python process communicate with Emacs.
The vulnerability arises because Python, by default,
prepends '' to the module search path, so modules are looked
for in the current directory. If the current directory is
world-writable, an attacker may insert malicious code by
adding a fake Python module named emacs.py into that
directory.
Discovery 2008-09-05 Entry 2008-11-07 Modified 2010-05-02 emacs
ge 22 le 22.2_1
CVE-2008-3949
http://lists.gnu.org/archive/html/emacs-devel/2008-09/msg00215.html
|
| c1e5f35e-f93d-11e1-b07f-00235a5f2c9a | emacs -- remote code execution vulnerability
Chong Yidong reports:
Paul Ling has found a security flaw in the file-local
variables code in GNU Emacs.
When the Emacs user option `enable-local-variables' is
set to `:safe' (the default value is t), Emacs should
automatically refuse to evaluate `eval' forms in file-local
variable sections. Due to the bug, Emacs instead
automatically evaluates such `eval' forms. Thus, if the user
changes the value of `enable-local-variables' to `:safe',
visiting a malicious file can cause automatic execution of
arbitrary Emacs Lisp code with the permissions of the
user.
The bug is present in Emacs 23.2, 23.3, 23.4, and
24.1.
Discovery 2012-08-13 Entry 2012-09-08 Modified 2012-09-23 emacs
gt 24.* lt 24.2
gt 23.* le 23.4_2
54969
CVE-2012-3479
https://lists.gnu.org/archive/html/emacs-devel/2012-08/msg00802.html
http://debbugs.gnu.org/cgi/bugreport.cgi?bug=12155
|
| c1e5f35e-f93d-11e1-b07f-00235a5f2c9a | emacs -- remote code execution vulnerability
Chong Yidong reports:
Paul Ling has found a security flaw in the file-local
variables code in GNU Emacs.
When the Emacs user option `enable-local-variables' is
set to `:safe' (the default value is t), Emacs should
automatically refuse to evaluate `eval' forms in file-local
variable sections. Due to the bug, Emacs instead
automatically evaluates such `eval' forms. Thus, if the user
changes the value of `enable-local-variables' to `:safe',
visiting a malicious file can cause automatic execution of
arbitrary Emacs Lisp code with the permissions of the
user.
The bug is present in Emacs 23.2, 23.3, 23.4, and
24.1.
Discovery 2012-08-13 Entry 2012-09-08 Modified 2012-09-23 emacs
gt 24.* lt 24.2
gt 23.* le 23.4_2
54969
CVE-2012-3479
https://lists.gnu.org/archive/html/emacs-devel/2012-08/msg00802.html
http://debbugs.gnu.org/cgi/bugreport.cgi?bug=12155
|
| 66657bd5-ac92-11dd-b541-001f3b19d541 | emacs -- run-python vulnerability
Emacs developers report:
The Emacs command `run-python' launches an interactive
Python interpreter. After the Python process starts up,
Emacs automatically sends it the line:
import emacs
which normally imports a script named emacs.py which is
distributed with Emacs. This script, which is typically
located in a write-protected installation directory with
other Emacs program files, defines various functions to help
the Python process communicate with Emacs.
The vulnerability arises because Python, by default,
prepends '' to the module search path, so modules are looked
for in the current directory. If the current directory is
world-writable, an attacker may insert malicious code by
adding a fake Python module named emacs.py into that
directory.
Discovery 2008-09-05 Entry 2008-11-07 Modified 2010-05-02 emacs
ge 22 le 22.2_1
CVE-2008-3949
http://lists.gnu.org/archive/html/emacs-devel/2008-09/msg00215.html
|