September 2, 2019
Exim is prone to an arbitrary code-execution vulnerability. An attacker can exploit this issue to execute arbitrary code with root privileges. Exim versions 4.8 through 4.92.1 are vulnerable.
- Exim Exim 4.80
- Exim Exim 4.80.1
- Exim Exim 4.82
- Exim Exim 4.82.1
- Exim Exim 4.83
- Exim Exim 4.84.2
- Exim Exim 4.85
- Exim Exim 4.85.2
- Exim Exim 4.86
- Exim Exim 4.86.2
- Exim Exim 4.87
- Exim Exim 4.88
- Exim Exim 4.89
- Exim Exim 4.90
- Exim Exim 4.90.1
- Exim Exim 4.91
- Exim Exim 4.92
- Exim Exim 4.92.1
- Redhat Enterprise Linux 5
- Ubuntu Ubuntu Linux 16.04 LTS
- Ubuntu Ubuntu Linux 18.04 LTS
- Ubuntu Ubuntu Linux 19.04
Permit local access for trusted individuals only. Where possible, use restricted environments and restricted shells.
Permit access to systems for trusted and accountable individuals only.
Block external access at the network boundary, unless external parties require service.
If global access isn't needed, filter access to the affected device at the network boundary. Restricting access to only trusted computers and networks might greatly reduce the likelihood of exploitation.
Deploy network intrusion detection systems to monitor network traffic for malicious activity.
Deploy NIDS to monitor network traffic for signs of anomalous or suspicious activity. This includes but is not limited to requests that include explained incoming and outgoing traffic. This may indicate exploit attempts to activity that results from successful exploits.
Implement multiple redundant layers of security.
Since this issue may be leveraged to execute code, we recommend memory-protection schemes, such as nonexecutable stack/heap configurations and randomly mapped memory segments. This tactic may complicate exploits of memory-corruption vulnerabilities.
Updates are available. Please see the references or vendor advisory for more information.
Zerons for the initial report, Qualys for the analysis
© 1995- Symantec Corporation
Permission to redistribute this alert electronically is granted as long as it is not edited in any way unless authorized by Symantec Security Response. Reprinting the whole or part of this alert in any medium other than electronically requires permission from firstname.lastname@example.org.
The information in the advisory is believed to be accurate at the time of publishing based on currently available information. Use of the information constitutes acceptance for use in an AS IS condition. There are no warranties with regard to this information. Neither the author nor the publisher accepts any liability for any direct, indirect, or consequential loss or damage arising from use of, or reliance on, this information.
Symantec, Symantec products, Symantec Security Response, and email@example.com are registered trademarks of Symantec Corp. and/or affiliated companies in the United States and other countries. All other registered and unregistered trademarks represented in this document are the sole property of their respective companies/owners.