Eli Zaretskii reported to emacs-devel mailing list, that emacs can execute arbitrary lisp code if fast-lock-mode is enabled and user opens source file (e.g. .c file) that is accompanied with crafted malicious .flc file. Issue is reported to affect both emacs and xemacs. References: http://thread.gmane.org/gmane.emacs.devel/96903 http://bugs.gentoo.org/show_bug.cgi?id=221197 http://tracker.xemacs.org/XEmacs/its/issue378
Steps to reproduce, as taken from reporter's mail: 1. Create .emacs with contents (global-font-lock-mode t) (seq font-lock-support-mode 'fast-lock-mode) 2. Create foo.c with contents /* Nothing to see here */ 3. Create foo.c.flc with contents (message "Something to see here!") 4. Start Emacs and load foo.c ---> Observe that code from foo.c.flc is run. Not good. (This is with Emacs 21.3.1; XEmacs is also affected, although step 1 needs to be adjusted.)
xemacs-packages-extra-20070427-2.fc9 has been submitted as an update for Fedora 9
xemacs-packages-extra-20070427-2.fc8 has been submitted as an update for Fedora 8
xemacs-packages-extra-20070427-2.fc9 has been pushed to the Fedora 9 stable repository. If problems still persist, please make note of it in this bug report.
xemacs-packages-extra-20070427-2.fc8 has been pushed to the Fedora 8 stable repository. If problems still persist, please make note of it in this bug report.
I wonder why this bug is still open, hasn't it been fixed a long time ago in all active distros?
This is left open for possible inclusion of the fix in the future emacs updates in RHEL-4 and RHEL-5. As Fedora package maintainer, you probably don't need to care, so feel free to un-CC yourself.
Statement: Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/.