4 matches found
emacs: arbitrary code execution via Lisp macro expansion
A flaw was found in Emacs. Viewing or editing an untrusted Emacs Lisp source code file can cause arbitrary code execution due to unsafe macro expansion when a user has configured elisp-completion-at-point for code completion or has enabled automatic error checking, such as Flymake or Flycheck...
emacs: arbitrary code execution via Lisp macro expansion
A flaw was found in Emacs. Viewing or editing an untrusted Emacs Lisp source code file can cause arbitrary code execution due to unsafe macro expansion when a user has configured elisp-completion-at-point for code completion or has enabled automatic error checking, such as Flymake or Flycheck...
emacs: arbitrary code execution via Lisp macro expansion
A flaw was found in Emacs. Viewing or editing an untrusted Emacs Lisp source code file can cause arbitrary code execution due to unsafe macro expansion when a user has configured elisp-completion-at-point for code completion or has enabled automatic error checking, such as Flymake or Flycheck...
The vulnerability of the elisp-completion-at-point() and elisp-flymake-byte-compile() functions in the EMACS text editor’s Lisp mode allows attackers to execute arbitrary code.
The vulnerability of the elisp-completion-at-point and elisp-flymake-byte-compile functions in the EMACS text editor’s Lisp mode is related to improper code generation management. Exploiting this vulnerability may allow a remote attacker to execute arbitrary code...