From $URL: Enriched mode implements an extension command to the text/enriched format called "x-display", which stores "display" text properties. It's possible to use this extension command to transparently execute arbitrary code in an Emacs process that opens a text/enriched file. Upstream issue: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=28350 Upstream patch: https://git.savannah.gnu.org/cgit/emacs.git/commit/?h=emacs-25&id=9ad0fcc54442a9a01d41be19880250783426db70 References: http://seclists.org/oss-sec/2017/q3/422
Fixed in slots 23, 24, and 25: emacs-23.4-r16 emacs-24.5-r4 emacs-25.2-r1 Slot 18 (emacs-18.59-r11) is _not_ affected, since the vulnerable code did not yet exist in version 18.
@arches, please proceed to stabilization, thank you! Daj Uan (jmbailey/mbailey_j) Gentoo Security Padawan
sparc is no longer a stable profile.
(In reply to Aaron Bauman from comment #3) > sparc is no longer a stable profile. But it has stable keywords. Readding to CC (as acked by its arch team).
Upstream has released emacs-25.3 containing the fix. Arch teams, note the updated package list: emacs-23.4-r16 emacs-24.5-r4 emacs-25.3
ia64 stable
(In reply to Ulrich Müller from comment #4) > (In reply to Aaron Bauman from comment #3) > > sparc is no longer a stable profile. > > But it has stable keywords. Readding to CC (as acked by its arch team). No, it is not longer security supported and is not a stable arch. Don't abstain from a vote then come running around trying to enforce policies on things you apparently don't understand.
(In reply to Aaron Bauman from comment #7) > (In reply to Ulrich Müller from comment #4) > > (In reply to Aaron Bauman from comment #3) > > > sparc is no longer a stable profile. > > > > But it has stable keywords. Readding to CC (as acked by its arch team). > > No, it is not longer security supported and is not a stable arch. Don't > abstain from a vote then come running around trying to enforce policies on > things you apparently don't understand. FYI: you answer does not make sense for me. We are clearly missing common ground. Let's continue in https://archives.gentoo.org/gentoo-dev/message/d733c56155140b54646a4714303bfc1c
Stable on alpha.
arm stable, tested by Yury German
hppa stable
ppc64 stable
ppc stable
x86 stable
amd64 stable
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=b950741cd641bbb454b13b81c591ac26f53b1884 commit b950741cd641bbb454b13b81c591ac26f53b1884 Author: Ulrich Müller <ulm@gentoo.org> AuthorDate: 2017-12-03 11:11:47 +0000 Commit: Ulrich Müller <ulm@gentoo.org> CommitDate: 2017-12-03 11:11:47 +0000 app-editors/emacs: Remove all vulnerable versions. Bug: https://bugs.gentoo.org/630680 Package-Manager: Portage-2.3.16, Repoman-2.3.6 app-editors/emacs/Manifest | 2 - app-editors/emacs/emacs-23.4-r15.ebuild | 346 ------------------------------- app-editors/emacs/emacs-24.5-r3.ebuild | 344 ------------------------------ app-editors/emacs/emacs-25.2.ebuild | 356 -------------------------------- 4 files changed, 1048 deletions(-)}
Stable on all security supported arches. @sparc: Removing you from CC here, please continue in bug 639598. All vulnerable versions have been removed.
glsa request has been filed
This issue was resolved and addressed in GLSA 201801-07 at https://security.gentoo.org/glsa/201801-07 by GLSA coordinator Aaron Bauman (b-man).