Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 1517680 - (CVE-2017-16943) CVE-2017-16943 exim: use-after-free in receive_msg function via vectors involving BDAT commands
CVE-2017-16943 exim: use-after-free in receive_msg function via vectors invol...
Status: CLOSED NOTABUG
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
urgent Severity urgent
: ---
: ---
Assigned To: Red Hat Product Security
impact=critical,public=20171123,repor...
: Security
Depends On: 1517686 1517687
Blocks:
  Show dependency treegraph
 
Reported: 2017-11-27 03:47 EST by Adam Mariš
Modified: 2017-11-27 04:02 EST (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-11-27 04:02:33 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Adam Mariš 2017-11-27 03:47:06 EST
The receive_msg function in receive.c in the SMTP daemon in Exim 4.88 and 4.89 allows remote attackers to execute arbitrary code or cause a denial of service (use-after-free) via vectors involving BDAT commands.

Upstream bug:

https://bugs.exim.org/show_bug.cgi?id=2199

Upstream patch:

https://git.exim.org/exim.git/commitdiff/4e6ae6235c68de243b1c2419027472d7659aa2b4
Comment 1 Adam Mariš 2017-11-27 03:54:14 EST
Created exim tracking bugs for this issue:

Affects: epel-all [bug 1517686]
Affects: fedora-all [bug 1517687]
Comment 2 Adam Mariš 2017-11-27 03:56:38 EST
Mitigation:

if you are running Exim 4.88 or newer, then in the main section of your Exim configuration, set:

chunking_advertise_hosts =

This disables advertising the ESMTP CHUNKING extension, making the BDAT verb unavailable and avoids letting an attacker apply the logic.

Note You need to log in before you can comment on or make changes to this bug.