From: "Bjørn Mork" <bjorn@mork.no>
To: soyeomul@doraji.xyz (Byung-Hee HWANG "(황병희, 黃炳熙)")
Cc: ding@gnus.org
Subject: Re: Security: Gnus & GNU Emacs 25.2 enriched text remote code execution
Date: Tue, 12 Sep 2017 11:48:47 +0200 [thread overview]
Message-ID: <87ingomem8.fsf@miraculix.mork.no> (raw)
In-Reply-To: <yw.u6fdf4e0b8ecd.1505189512.fsf@lambda.alex.chromebook> ("Byung-Hee HWANG =?utf-8?B?XCIo7Zmp67OR7Z2sLCDpu4PngrPnhpkpXCIiJ3M=?= message of "Tue, 12 Sep 2017 13:14:50 +0900")
soyeomul@doraji.xyz (Byung-Hee HWANG "(황병희, 黃炳熙)") writes:
> In Article <yzsvakodhkv.fsf@marauder.physik.uni-ulm.de>,
> Reiner Steib <reinersteib@gmail.com> writes:
>
>> Emacs 25.3 is an emergency release to fix a security vulnerability
>> that is exploitable remotely in Emacs-based mail clients (such as
>> Gnus).
>>
>> Please update to Emacs 25.3 as soon as possible:
>> http://lists.gnu.org/archive/html/info-gnu-emacs/2017-09/msg00000.html
>>
>> To work around the bug in Emacs versions before 25.3, put the
>> following code in your personal or site-wide Emacs init file
>> (~/.emacs, ~/emacs.d/init.el, site-start.el):
>>
>> (eval-after-load "enriched"
>> '(defun enriched-decode-display-prop (start end &optional param)
>> (list start end)))
>>
>> See also <http://www.openwall.com/lists/oss-security/2017/09/11/1>.
>
> By the way, my emacs version is 23.3. Gnus version Ma Gnus 0.15. Hey i am
> dangerous? Please ...
Quoting from the announcement referred to above:
"This vulnerability was introduced in Emacs 19.29."
So, yes, your emacs version is vulnerable.
Bjørn
next prev parent reply other threads:[~2017-09-12 9:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-11 21:57 Reiner Steib
2017-09-12 4:14 ` Byung-Hee HWANG (황병희, 黃炳熙)
2017-09-12 9:48 ` Bjørn Mork [this message]
2017-09-12 11:31 ` Byung-Hee HWANG (황병희, 黃炳熙)
2017-09-14 14:44 ` Ted Zlatanov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ingomem8.fsf@miraculix.mork.no \
--to=bjorn@mork.no \
--cc=ding@gnus.org \
--cc=soyeomul@doraji.xyz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).