Bug 146706

Summary: CAN-2005-0100 Arbitrary code execution in *emacs*
Product: Red Hat Enterprise Linux 4 Reporter: Josh Bressers <bressers>
Component: xemacsAssignee: Jens Petersen <petersen>
Status: CLOSED ERRATA QA Contact: David Lawrence <dkl>
Severity: high Docs Contact:
Priority: medium    
Version: 4.0CC: security-response-team
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard: impact=important,public=20050206
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2005-02-15 09:42:30 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 142822    

Description Josh Bressers 2005-01-31 21:32:02 UTC
*** This bug has been split off bug 146704 ***

------- Original comment by Josh Bressers (Security Response Team) on 2005.01.31
16:18 -------

Max Vozeler discovered several format string vulnerabilities in the
movemail utility of Emacs, the well-known editor.  Via connecting to a
malicious POP server an attacker can execute arbitrary code under the
privileges of group mail (or worse, depending on the permissions of
the movemail binary).


The proposed fix for this issue is attachment 110461 [details]

Comment 1 Mark J. Cox 2005-02-03 14:53:41 UTC
According to vendor-sec

"The date has been moved to February 6th and XEmacs21 21.4.17 will
be released including the correction on the same day."


Comment 3 Mark J. Cox 2005-02-07 09:17:56 UTC
http://list-archive.xemacs.org/xemacs-announce/200502/msg00001.html
Removing embargo

Comment 4 Mark J. Cox 2005-02-15 09:42:30 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHSA-2005-133.html