openSUSE: 2021:0754-1 critical: exim
Description
This update for exim fixes the following issues:
Exim was updated to exim-4.94.2
security update (boo#1185631)
* CVE-2020-28007: Link attack in Exim's log directory
* CVE-2020-28008: Assorted attacks in Exim's spool directory
* CVE-2020-28014: Arbitrary PID file creation
* CVE-2020-28011: Heap buffer overflow in queue_run()
* CVE-2020-28010: Heap out-of-bounds write in main()
* CVE-2020-28013: Heap buffer overflow in parse_fix_phrase()
* CVE-2020-28016: Heap out-of-bounds write in parse_fix_phrase()
* CVE-2020-28015: New-line injection into spool header file (local)
* CVE-2020-28012: Missing close-on-exec flag for privileged pipe
* CVE-2020-28009: Integer overflow in get_stdinput()
* CVE-2020-28017: Integer overflow in receive_add_recipient()
* CVE-2020-28020: Integer overflow in receive_msg()
* CVE-2020-28023: Out-of-bounds read in smtp_setup_msg()
* CVE-2020-28021: New-line injection into spool header file (remote)
* CVE-2020-28022: Heap out-of-bounds read and write in extract_option()
* CVE-2020-28026: Line truncation and injection in spool_read_header()
* CVE-2020-28019: Failure to reset function pointer after BDAT error
* CVE-2020-28024: Heap buffer underflow in smtp_ungetc()
* CVE-2020-28018: Use-after-free in tls-openssl.c
* CVE-2020-28025: Heap out-of-bounds read in pdkim_finish_bodyhash()
update to exim-4.94.1
* Fix security issue in BDAT state confusion. Ensure we reset known-good
where we know we need to not be reading BDAT data, as a general case
fix, and move the places where we switch to BDAT mode until after
various protocol state checks. Fixes CVE-2020-BDATA reported by Qualys.
* Fix security issue in SMTP verb option parsing (CVE-2020-EXOPT)
* Fix security issue with too many recipients on a message (to remove a
known security problem if someone does set recipients_max to unlimited,
or if local additions add to the recipient list). Fixes CVE-2020-RCPTL
reported by Qualys.
* Fix CVE-2020-28016 (PFPZA): Heap out-of-bounds write in
parse_fix_phrase()
* Fix security issue CVE-2020-PFPSN and guard against cmdline invoker
providing a particularly obnoxious sender full name.
* Fix Linux security issue CVE-2020-SLCWD and guard against PATH_MAX
better.
- bring back missing exim_db.8 manual page (fixes boo#1173693)
- bring in changes from current +fixes (lots of taint check fixes)
* Bug 1329: Fix format of Maildir-format filenames to match other mail-
related applications. Previously an "H" was used where available info
says that "M" should be, so change to match.
* Bug 2587: Fix pam expansion condition. Tainted values are commonly
used as arguments, so an implementation trying to copy these into a
local buffer was taking a taint-enforcement trap. Fix by using
dynamically created buffers.
* Bug 2586: Fix listcount expansion operator. Using tainted arguments
is reasonable, eg. to count headers. Fix by using dynamically created
buffers rather than a local. Do similar fixes for ACL actions "dcc",
"log_reject_target", "malware" and "spam"; the arguments are expanded
so could be handling tainted values.
* Bug 2590: Fix -bi (newaliases). A previous code rearrangement had
broken the (no-op) support for this sendmail command. Restore it to
doing nothing, silently, and returning good status.
- update to exim 4.94
* some transports now refuse to use tainted data in constructing their
delivery location this WILL BREAK configurations which are not updated
accordingly. In particular: any Transport use of $local_user which has
been relying upon check_local_user far away in the Router to make it
safe, should be updated to replace $local_user with $local_part_data.
* Attempting to remove, in router or transport, a header name that ends
with an asterisk (which is a standards-legal name) will now result in
all headers named starting with the string before the asterisk being
removed.
- switch pretrans to use lua (fixes boo#1171877)
- bring changes from current in +fixes branch
(patch-exim-fixes-ee83de04d3087efaf808d1f2235a988275c2ee94)
* fixes CVE-2020-12783 (boo#1171490)
* Regard command-line recipients as tainted.
* Bug 2489: Fix crash in the "pam" expansion condition.
* Use tainted buffers for the transport smtp context.
* Bug 2493: Harden ARC verify against Outlook, which has been seen to
mix the ordering of its ARC headers. This caused a crash.
* Bug 2492: Use tainted memory for retry record when needed. Previously
when a new record was being constructed with information from the
peer, a trap was taken.
* Bug 2494: Unset the default for dmarc_tld_file.
* Fix an uninitialised flag in early-pipelining. Previously connections
could, depending on the platform, hang at the STARTTLS response.
* Bug 2498: Reset a counter used for ARC verify before handling another
message on a connection. Previously if one message had ARC headers and the following one did not, a crash could result when adding an
Authentication-Results: header.
* Bug 2500: Rewind some of the common-coding in string handling between
the Exim main code and Exim-related utities.
* Fix the variables set by the gsasl authenticator.
* Bug 2507: Modules: on handling a dynamic-module (lookups) open failure,
only retrieve the errormessage once.
* Bug 2501: Fix init call in the heimdal authenticator. Previously it
adjusted the size of a major service buffer; this failed because the
buffer was in use at the time. Change to a compile-time increase in
the buffer size, when this authenticator is compiled into exim.
- update to exim 4.93.0.4 (+fixes release)
* Avoid costly startup code when not strictly needed. This reduces time
for some exim process initialisations. It does mean that the logging
of TLS configuration problems is only done for the daemon startup.
* Early-pipelining support code is now included unless disabled in
Makefile.
* DKIM verification defaults no long accept sha1 hashes, to conform to
RFC 8301. They can still be enabled, using the dkim_verify_hashes main
option.
* Support CHUNKING from an smtp transport using a transport_filter, when
DKIM signing is being done. Previously a transport_filter would
always disable CHUNKING, falling back to traditional DATA.
* Regard command-line receipients as tainted.
* Bug 340: Remove the daemon pid file on exit, whe due to SIGTERM.
* Bug 2489: Fix crash in the "pam" expansion condition. It seems that
the PAM library frees one of the arguments given to it, despite the
documentation. Therefore a plain malloc must be used.
* Bug 2491: Use tainted buffers for the transport smtp context.
Previously
on-stack buffers were used, resulting in a taint trap when DSN
information copied from a received message was written into the
buffer.
* Bug 2493: Harden ARC verify against Outlook, whick has been seen to
mix the ordering of its ARC headers. This caused a crash.
* Bug 2492: Use tainted memory for retry record when needed. Previously
when a new record was being constructed with information from the
peer, a trap was taken.
* Bug 2494: Unset the default for dmarc_tld_file. Previously a naiive
installation would get error messages from DMARC verify, when it hit
the nonexistent file indicated by the default. Distros wanting DMARC
enabled should both provide the file and set the option. Also enforce
no DMARC verification for command-line sourced messages.
* Fix an uninitialised flag in early-pipelining. Previously connections
could, depending on the platform, hang at the STARTTLS response.
* Bug 2498: Reset a counter used for ARC verify before handling another
message on a connection. Previously if one message had ARC headers and the following one did not, a crash could result when adding an
Authentication-Results: header.
* Bug 2500: Rewind some of the common-coding in string handling between
the Exim main code and Exim-related utities. The introduction of
taint tracking also did many adjustments to string handling. Since
then, eximon frequently terminated with an assert failure.
* When PIPELINING, synch after every hundred or so RCPT commands sent
and check for 452 responses. This slightly helps the inefficieny of
doing a large alias-expansion into a recipient-limited target. The
max_rcpt transport option still applies (and at the current default,
will override the new feature). The check is done for either cause of
synch, and forces a fast-retry of all 452'd recipients using a new
MAIL FROM on the same connection. The new facility is not tunable at
this time.
* Fix the variables set by the gsasl authenticator. Previously a
pointer to library live data was being used, so the results became
garbage. Make copies while it is still usable.
* Logging: when the deliver_time selector ise set, include the DT= field
on delivery deferred (==) and failed (**) lines (if a delivery was
attemtped). Previously it was only on completion (=>) lines.
* Authentication: the gsasl driver not provides the $authN variables in
time for the expansion of the server_scram_iter and server_scram_salt
options.
spec file cleanup to make update work
- add docdir to spec
- update to exim 4.93
* SUPPORT_DMARC replaces EXPERIMENTAL_DMARC
* DISABLE_TLS replaces SUPPORT_TLS
* Bump the version for the local_scan API.
* smtp transport option hosts_try_fastopen defaults to "*".
* DNSSec is requested (not required) for all queries. (This seemes to
ask for trouble if your resolver is a systemd-resolved.)
* Generic router option retry_use_local_part defaults to "true" under
specific pre-conditions.
* Introduce a tainting mechanism for values read from untrusted sources.
* Use longer file names for temporary spool files (this avoids name
conflicts with spool on a shared file system).
* Use dsn_from main config option (was ignored previously).
- update to exim 4.92.3
* CVE-2019-16928: fix against Heap-based buffer overflow in
string_vformat, remote code execution seems to be possible
- update to exim 4.92.2
* CVE-2019-15846: fix against remote attackers executing arbitrary code
as root via a trailing backslash
- update to exim 4.92.1
* CVE-2019-13917: Fixed an issue with ${sort} expansion which could allow
remote attackers to execute other programs with root privileges
(boo#1142207)
- spec file cleanup
* fix DANE inclusion guard condition
* re-enable i18n and remove misleading comment
* EXPERIMENTAL_SPF is now SUPPORT_SPF
* DANE is now SUPPORT_DANE
- update to exim 4.92
* ${l_header:
Patch
Patch Instructions: To install this openSUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". Alternatively you can run the command listed for your product: - openSUSE Backports SLE-15-SP2: zypper in -t patch openSUSE-2021-754=1
Package List
- openSUSE Backports SLE-15-SP2 (aarch64 ppc64le s390x x86_64): exim-4.94.2-bp152.6.4.1 eximon-4.94.2-bp152.6.4.1 eximstats-html-4.94.2-bp152.6.4.1 libspf2-2-1.2.10-bp152.5.1 libspf2-2-debuginfo-1.2.10-bp152.5.1 libspf2-debuginfo-1.2.10-bp152.5.1 libspf2-debugsource-1.2.10-bp152.5.1 libspf2-devel-1.2.10-bp152.5.1 libspf2-tools-1.2.10-bp152.5.1 libspf2-tools-debuginfo-1.2.10-bp152.5.1
References
https://www.suse.com/security/cve/CVE-2017-1000369.html https://www.suse.com/security/cve/CVE-2017-16943.html https://www.suse.com/security/cve/CVE-2017-16944.html https://www.suse.com/security/cve/CVE-2018-6789.html https://www.suse.com/security/cve/CVE-2019-16928.html https://www.suse.com/security/cve/CVE-2020-12783.html https://www.suse.com/security/cve/CVE-2020-28007.html https://www.suse.com/security/cve/CVE-2020-28008.html https://www.suse.com/security/cve/CVE-2020-28009.html https://www.suse.com/security/cve/CVE-2020-28010.html https://www.suse.com/security/cve/CVE-2020-28011.html https://www.suse.com/security/cve/CVE-2020-28012.html https://www.suse.com/security/cve/CVE-2020-28013.html https://www.suse.com/security/cve/CVE-2020-28014.html https://www.suse.com/security/cve/CVE-2020-28015.html https://www.suse.com/security/cve/CVE-2020-28016.html https://www.suse.com/security/cve/CVE-2020-28017.html https://www.suse.com/security/cve/CVE-2020-28018.html https://www.suse.com/security/cve/CVE-2020-28019.html https://www.suse.com/security/cve/CVE-2020-28020.html https://www.suse.com/security/cve/CVE-2020-28021.html https://www.suse.com/security/cve/CVE-2020-28022.html https://www.suse.com/security/cve/CVE-2020-28023.html https://www.suse.com/security/cve/CVE-2020-28024.html https://www.suse.com/security/cve/CVE-2020-28025.html https://www.suse.com/security/cve/CVE-2020-28026.html https://bugzilla.suse.com/1079832 https://bugzilla.suse.com/1171490 https://bugzilla.suse.com/1171877 https://bugzilla.suse.com/1173693 https://bugzilla.suse.com/1185631
