ID CVE-2010-4345
Summary Exim 4.72 and earlier allows local users to gain privileges by leveraging the ability of the exim user account to specify an alternate configuration file with a directive that contains arbitrary commands, as demonstrated by the spool_directory directive.
References
Vulnerable Configurations
  • University of Cambridge Exim 2.10
    cpe:2.3:a:exim:exim:2.10
  • University of Cambridge Exim 2.11
    cpe:2.3:a:exim:exim:2.11
  • University of Cambridge Exim 2.12
    cpe:2.3:a:exim:exim:2.12
  • University of Cambridge Exim 3.00
    cpe:2.3:a:exim:exim:3.00
  • University of Cambridge Exim 3.01
    cpe:2.3:a:exim:exim:3.01
  • University of Cambridge Exim 3.02
    cpe:2.3:a:exim:exim:3.02
  • University of Cambridge Exim 3.03
    cpe:2.3:a:exim:exim:3.03
  • University of Cambridge Exim 3.10
    cpe:2.3:a:exim:exim:3.10
  • University of Cambridge Exim 3.11
    cpe:2.3:a:exim:exim:3.11
  • University of Cambridge Exim 3.12
    cpe:2.3:a:exim:exim:3.12
  • University of Cambridge Exim 3.13
    cpe:2.3:a:exim:exim:3.13
  • University of Cambridge Exim 3.14
    cpe:2.3:a:exim:exim:3.14
  • University of Cambridge Exim 3.15
    cpe:2.3:a:exim:exim:3.15
  • University of Cambridge Exim 3.16
    cpe:2.3:a:exim:exim:3.16
  • University of Cambridge Exim 3.20
    cpe:2.3:a:exim:exim:3.20
  • University of Cambridge Exim 3.21
    cpe:2.3:a:exim:exim:3.21
  • University of Cambridge Exim 3.22
    cpe:2.3:a:exim:exim:3.22
  • University of Cambridge Exim 3.30
    cpe:2.3:a:exim:exim:3.30
  • University of Cambridge Exim 3.31
    cpe:2.3:a:exim:exim:3.31
  • University of Cambridge Exim 3.32
    cpe:2.3:a:exim:exim:3.32
  • University of Cambridge Exim 3.33
    cpe:2.3:a:exim:exim:3.33
  • University of Cambridge Exim 3.34
    cpe:2.3:a:exim:exim:3.34
  • University of Cambridge Exim 3.35
    cpe:2.3:a:exim:exim:3.35
  • University of Cambridge Exim 3.36
    cpe:2.3:a:exim:exim:3.36
  • University of Cambridge Exim 4.00
    cpe:2.3:a:exim:exim:4.00
  • University of Cambridge Exim 4.01
    cpe:2.3:a:exim:exim:4.01
  • University of Cambridge Exim 4.02
    cpe:2.3:a:exim:exim:4.02
  • University of Cambridge Exim 4.03
    cpe:2.3:a:exim:exim:4.03
  • University of Cambridge Exim 4.04
    cpe:2.3:a:exim:exim:4.04
  • University of Cambridge Exim 4.05
    cpe:2.3:a:exim:exim:4.05
  • University of Cambridge Exim 4.10
    cpe:2.3:a:exim:exim:4.10
  • University of Cambridge Exim 4.11
    cpe:2.3:a:exim:exim:4.11
  • University of Cambridge Exim 4.12
    cpe:2.3:a:exim:exim:4.12
  • University of Cambridge Exim 4.14
    cpe:2.3:a:exim:exim:4.14
  • University of Cambridge Exim 4.20
    cpe:2.3:a:exim:exim:4.20
  • University of Cambridge Exim 4.21
    cpe:2.3:a:exim:exim:4.21
  • University of Cambridge Exim 4.22
    cpe:2.3:a:exim:exim:4.22
  • University of Cambridge Exim 4.23
    cpe:2.3:a:exim:exim:4.23
  • University of Cambridge Exim 4.24
    cpe:2.3:a:exim:exim:4.24
  • University of Cambridge Exim 4.30
    cpe:2.3:a:exim:exim:4.30
  • University of Cambridge Exim 4.31
    cpe:2.3:a:exim:exim:4.31
  • University of Cambridge Exim 4.32
    cpe:2.3:a:exim:exim:4.32
  • University of Cambridge Exim 4.33
    cpe:2.3:a:exim:exim:4.33
  • University of Cambridge Exim 4.34
    cpe:2.3:a:exim:exim:4.34
  • University of Cambridge Exim 4.40
    cpe:2.3:a:exim:exim:4.40
  • University of Cambridge Exim 4.41
    cpe:2.3:a:exim:exim:4.41
  • University of Cambridge Exim 4.42
    cpe:2.3:a:exim:exim:4.42
  • University of Cambridge Exim 4.43
    cpe:2.3:a:exim:exim:4.43
  • University of Cambridge Exim 4.44
    cpe:2.3:a:exim:exim:4.44
  • University of Cambridge Exim 4.50
    cpe:2.3:a:exim:exim:4.50
  • University of Cambridge Exim 4.51
    cpe:2.3:a:exim:exim:4.51
  • University of Cambridge Exim 4.52
    cpe:2.3:a:exim:exim:4.52
  • University of Cambridge Exim 4.53
    cpe:2.3:a:exim:exim:4.53
  • University of Cambridge Exim 4.54
    cpe:2.3:a:exim:exim:4.54
  • University of Cambridge Exim 4.60
    cpe:2.3:a:exim:exim:4.60
  • University of Cambridge Exim 4.61
    cpe:2.3:a:exim:exim:4.61
  • University of Cambridge Exim 4.62
    cpe:2.3:a:exim:exim:4.62
  • University of Cambridge Exim 4.63
    cpe:2.3:a:exim:exim:4.63
  • University of Cambridge Exim 4.64
    cpe:2.3:a:exim:exim:4.64
  • University of Cambridge Exim 4.65
    cpe:2.3:a:exim:exim:4.65
  • University of Cambridge Exim 4.66
    cpe:2.3:a:exim:exim:4.66
  • University of Cambridge Exim 4.67
    cpe:2.3:a:exim:exim:4.67
  • University of Cambridge Exim 4.68
    cpe:2.3:a:exim:exim:4.68
  • University of Cambridge Exim 4.69
    cpe:2.3:a:exim:exim:4.69
  • University of Cambridge Exim 4.70
    cpe:2.3:a:exim:exim:4.70
  • University of Cambridge Exim 4.71
    cpe:2.3:a:exim:exim:4.71
  • University of Cambridge Exim 4.72
    cpe:2.3:a:exim:exim:4.72
CVSS
Base: 6.9 (as of 14-12-2010 - 13:26)
Impact:
Exploitability:
CWE CWE-264
CAPEC
  • Accessing, Modifying or Executing Executable Files
    An attack of this type exploits a system's configuration that allows an attacker to either directly access an executable file, for example through shell access; or in a possible worst case allows an attacker to upload a file and then execute it. Web servers, ftp servers, and message oriented middleware systems which have many integration points are particularly vulnerable, because both the programmers and the administrators must be in synch regarding the interfaces and the correct privileges for each interface.
  • Leverage Executable Code in Non-Executable Files
    An attack of this type exploits a system's trust in configuration and resource files, when the executable loads the resource (such as an image file or configuration file) the attacker has modified the file to either execute malicious code directly or manipulate the target process (e.g. application server) to execute based on the malicious configuration parameters. Since systems are increasingly interrelated mashing up resources from local and remote sources the possibility of this attack occurring is high. The attack can be directed at a client system, such as causing buffer overrun through loading seemingly benign image files, as in Microsoft Security Bulletin MS04-028 where specially crafted JPEG files could cause a buffer overrun once loaded into the browser. Another example targets clients reading pdf files. In this case the attacker simply appends javascript to the end of a legitimate url for a pdf (http://www.gnucitizen.org/blog/danger-danger-danger/) http://path/to/pdf/file.pdf#whatever_name_you_want=javascript:your_code_here The client assumes that they are reading a pdf, but the attacker has modified the resource and loaded executable javascript into the client's browser process. The attack can also target server processes. The attacker edits the resource or configuration file, for example a web.xml file used to configure security permissions for a J2EE app server, adding role name "public" grants all users with the public role the ability to use the administration functionality. The server trusts its configuration file to be correct, but when they are manipulated, the attacker gains full control.
  • Blue Boxing
    This type of attack against older telephone switches and trunks has been around for decades. A tone is sent by an adversary to impersonate a supervisor signal which has the effect of rerouting or usurping command of the line. While the US infrastructure proper may not contain widespread vulnerabilities to this type of attack, many companies are connected globally through call centers and business process outsourcing. These international systems may be operated in countries which have not upgraded Telco infrastructure and so are vulnerable to Blue boxing. Blue boxing is a result of failure on the part of the system to enforce strong authorization for administrative functions. While the infrastructure is different than standard current applications like web applications, there are historical lessons to be learned to upgrade the access control for administrative functions.
  • Restful Privilege Elevation
    Rest uses standard HTTP (Get, Put, Delete) style permissions methods, but these are not necessarily correlated generally with back end programs. Strict interpretation of HTTP get methods means that these HTTP Get services should not be used to delete information on the server, but there is no access control mechanism to back up this logic. This means that unless the services are properly ACL'd and the application's service implementation are following these guidelines then an HTTP request can easily execute a delete or update on the server side. The attacker identifies a HTTP Get URL such as http://victimsite/updateOrder, which calls out to a program to update orders on a database or other resource. The URL is not idempotent so the request can be submitted multiple times by the attacker, additionally, the attacker may be able to exploit the URL published as a Get method that actually performs updates (instead of merely retrieving data). This may result in malicious or inadvertent altering of data on the server.
  • Target Programs with Elevated Privileges
    This attack targets programs running with elevated privileges. The attacker would try to leverage a bug in the running program and get arbitrary code to execute with elevated privileges. For instance an attacker would look for programs that write to the system directories or registry keys (such as HKLM, which stores a number of critical Windows environment variables). These programs are typically running with elevated privileges and have usually not been designed with security in mind. Such programs are excellent exploit targets because they yield lots of power when they break. The malicious user try to execute its code at the same level as a privileged system call.
  • Manipulating Input to File System Calls
    An attacker manipulates inputs to the target software which the target software passes to file system calls in the OS. The goal is to gain access to, and perhaps modify, areas of the file system that the target software did not intend to be accessible.
Access
VectorComplexityAuthentication
LOCAL MEDIUM NONE
Impact
ConfidentialityIntegrityAvailability
COMPLETE COMPLETE COMPLETE
exploit-db via4
description Exim4. CVE-2010-4344,CVE-2010-4345. Remote exploit for linux platform
id EDB-ID:16925
last seen 2016-02-02
modified 2010-12-16
published 2010-12-16
reporter metasploit
source https://www.exploit-db.com/download/16925/
title Exim4 <= 4.69 - string_format Function Heap Buffer Overflow
metasploit via4
description This module exploits a heap buffer overflow within versions of Exim prior to version 4.69. By sending a specially crafted message, an attacker can corrupt the heap and execute arbitrary code with the privileges of the Exim daemon. The root cause is that no check is made to ensure that the buffer is not full prior to handling '%s' format specifiers within the 'string_vformat' function. In order to trigger this issue, we get our message rejected by sending a message that is too large. This will call into log_write to log rejection headers (which is a default configuration setting). After filling the buffer, a long header string is sent. In a successful attempt, it overwrites the ACL for the 'MAIL FROM' command. By sending a second message, the string we sent will be evaluated with 'expand_string' and arbitrary shell commands can be executed. It is likely that this issue could also be exploited using other techniques such as targeting in-band heap management structures, or perhaps even function pointers stored in the heap. However, these techniques would likely be far more platform specific, more complicated, and less reliable. This bug was original found and reported in December 2008, but was not properly handled as a security issue. Therefore, there was a 2 year lag time between when the issue was fixed and when it was discovered being exploited in the wild. At that point, the issue was assigned a CVE and began being addressed by downstream vendors. An additional vulnerability, CVE-2010-4345, was also used in the attack that led to the discovery of danger of this bug. This bug allows a local user to gain root privileges from the Exim user account. If the Perl interpreter is found on the remote system, this module will automatically exploit the secondary bug as well to get root.
id MSF:EXPLOIT/UNIX/SMTP/EXIM4_STRING_FORMAT
last seen 2019-02-23
modified 2018-09-15
published 2010-12-11
reliability Excellent
reporter Rapid7
source https://github.com/rapid7/metasploit-framework/blob/master/modules/exploits/unix/smtp/exim4_string_format.rb
title Exim4 string_format Function Heap Buffer Overflow
nessus via4
  • NASL family CentOS Local Security Checks
    NASL id CENTOS_RHSA-2011-0153.NASL
    description Updated exim packages that fix one security issue are now available for Red Hat Enterprise Linux 4 and 5. The Red Hat Security Response Team has rated this update as having moderate security impact. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available from the CVE link in the References section. Exim is a mail transport agent (MTA) developed at the University of Cambridge for use on UNIX systems connected to the Internet. A privilege escalation flaw was discovered in Exim. If an attacker were able to gain access to the 'exim' user, they could cause Exim to execute arbitrary commands as the root user. (CVE-2010-4345) This update adds a new configuration file, '/etc/exim/trusted-configs'. To prevent Exim from running arbitrary commands as root, Exim will now drop privileges when run with a configuration file not listed as trusted. This could break backwards compatibility with some Exim configurations, as the trusted-configs file only trusts '/etc/exim/exim.conf' and '/etc/exim/exim4.conf' by default. If you are using a configuration file not listed in the new trusted-configs file, you will need to add it manually. Additionally, Exim will no longer allow a user to execute exim as root with the -D command line option to override macro definitions. All macro definitions that require root permissions must now reside in a trusted configuration file. Users of Exim are advised to upgrade to these updated packages, which contain a backported patch to correct this issue. After installing this update, the exim daemon will be restarted automatically.
    last seen 2019-02-21
    modified 2018-11-28
    plugin id 51785
    published 2011-01-28
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=51785
    title CentOS 4 / 5 : exim (CESA-2011:0153)
  • NASL family Ubuntu Local Security Checks
    NASL id UBUNTU_USN-1060-1.NASL
    description It was discovered that Exim contained a design flaw in the way it processed alternate configuration files. An attacker that obtained privileges of the 'Debian-exim' user could use an alternate configuration file to obtain root privileges. (CVE-2010-4345) It was discovered that Exim incorrectly handled certain return values when handling logging. An attacker that obtained privileges of the 'Debian-exim' user could use this flaw to obtain root privileges. (CVE-2011-0017) Dan Rosenberg discovered that Exim incorrectly handled writable sticky-bit mail directories. If Exim were configured in this manner, a local user could use this flaw to cause a denial of service or possibly gain privileges. This issue only applied to Ubuntu 6.06 LTS, 8.04 LTS, 9.10, and 10.04 LTS. (CVE-2010-2023) Dan Rosenberg discovered that Exim incorrectly handled MBX locking. If Exim were configured in this manner, a local user could use this flaw to cause a denial of service or possibly gain privileges. This issue only applied to Ubuntu 6.06 LTS, 8.04 LTS, 9.10, and 10.04 LTS. (CVE-2010-2024). Note that Tenable Network Security has extracted the preceding description block directly from the Ubuntu security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.
    last seen 2019-02-21
    modified 2018-12-01
    plugin id 51954
    published 2011-02-11
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=51954
    title Ubuntu 6.06 LTS / 8.04 LTS / 9.10 / 10.04 LTS / 10.10 : exim4 vulnerabilities (USN-1060-1)
  • NASL family SuSE Local Security Checks
    NASL id SUSE_11_3_EXIM-101211.NASL
    description remote attackers could trick exim into running arbitrary code (CVE-2010-4344). A privilege escalation flaw allowed attackers to gain root access (CVE-2010-4345).
    last seen 2019-02-21
    modified 2018-11-10
    plugin id 75481
    published 2014-06-13
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=75481
    title openSUSE Security Update : exim (openSUSE-SU-2010:1052-1)
  • NASL family SuSE Local Security Checks
    NASL id SUSE_11_1_EXIM-101211.NASL
    description remote attackers could trick exim into running arbitrary code (CVE-2010-4344). A privilege escalation flaw allowed attackers to gain root access (CVE-2010-4345).
    last seen 2019-02-21
    modified 2018-11-10
    plugin id 53657
    published 2011-05-05
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=53657
    title openSUSE Security Update : exim (openSUSE-SU-2010:1052-1)
  • NASL family Scientific Linux Local Security Checks
    NASL id SL_20110117_EXIM_ON_SL4_X.NASL
    description A privilege escalation flaw was discovered in Exim. If an attacker were able to gain access to the 'exim' user, they could cause Exim to execute arbitrary commands as the root user. (CVE-2010-4345) This update adds a new configuration file, '/etc/exim/trusted-configs'. To prevent Exim from running arbitrary commands as root, Exim will now drop privileges when run with a configuration file not listed as trusted. This could break backwards compatibility with some Exim configurations, as the trusted-configs file only trusts '/etc/exim/exim.conf' and '/etc/exim/exim4.conf' by default. If you are using a configuration file not listed in the new trusted-configs file, you will need to add it manually. Additionally, Exim will no longer allow a user to execute exim as root with the -D command line option to override macro definitions. All macro definitions that require root permissions must now reside in a trusted configuration file. After installing this update, the exim daemon will be restarted automatically.
    last seen 2019-02-21
    modified 2018-12-31
    plugin id 60936
    published 2012-08-01
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=60936
    title Scientific Linux Security Update : exim on SL4.x, SL5.x i386/x86_64
  • NASL family Debian Local Security Checks
    NASL id DEBIAN_DSA-2154.NASL
    description A design flaw (CVE-2010-4345 ) in exim4 allowed the local Debian-exim user to obtain root privileges by specifying an alternate configuration file using the -C option or by using the macro override facility (-D option). Unfortunately, fixing this vulnerability is not possible without some changes in exim4's behaviour. If you use the -C or -D options or use the system filter facility, you should evaluate the changes carefully and adjust your configuration accordingly. The Debian default configuration is not affected by the changes. The detailed list of changes is described in the NEWS.Debian file in the packages. The relevant sections are also reproduced below. In addition to that, missing error handling for the setuid/setgid system calls allowed the Debian-exim user to cause root to append log data to arbitrary files (CVE-2011-0017 ).
    last seen 2019-02-21
    modified 2018-11-10
    plugin id 51819
    published 2011-01-31
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=51819
    title Debian DSA-2154-1 : exim4 - privilege escalation
  • NASL family Oracle Linux Local Security Checks
    NASL id ORACLELINUX_ELSA-2011-0153.NASL
    description From Red Hat Security Advisory 2011:0153 : Updated exim packages that fix one security issue are now available for Red Hat Enterprise Linux 4 and 5. The Red Hat Security Response Team has rated this update as having moderate security impact. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available from the CVE link in the References section. Exim is a mail transport agent (MTA) developed at the University of Cambridge for use on UNIX systems connected to the Internet. A privilege escalation flaw was discovered in Exim. If an attacker were able to gain access to the 'exim' user, they could cause Exim to execute arbitrary commands as the root user. (CVE-2010-4345) This update adds a new configuration file, '/etc/exim/trusted-configs'. To prevent Exim from running arbitrary commands as root, Exim will now drop privileges when run with a configuration file not listed as trusted. This could break backwards compatibility with some Exim configurations, as the trusted-configs file only trusts '/etc/exim/exim.conf' and '/etc/exim/exim4.conf' by default. If you are using a configuration file not listed in the new trusted-configs file, you will need to add it manually. Additionally, Exim will no longer allow a user to execute exim as root with the -D command line option to override macro definitions. All macro definitions that require root permissions must now reside in a trusted configuration file. Users of Exim are advised to upgrade to these updated packages, which contain a backported patch to correct this issue. After installing this update, the exim daemon will be restarted automatically.
    last seen 2019-02-21
    modified 2019-01-02
    plugin id 68180
    published 2013-07-12
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=68180
    title Oracle Linux 4 / 5 : exim (ELSA-2011-0153)
  • NASL family Gentoo Local Security Checks
    NASL id GENTOO_GLSA-201401-32.NASL
    description The remote host is affected by the vulnerability described in GLSA-201401-32 (Exim: Multiple vulnerabilities) Multiple vulnerabilities have been discovered in Exim. Please review the CVE identifiers referenced below for details. Impact : A remote attacker could possibly execute arbitrary code with root privileges, or cause a Denial of Service condition. Workaround : There is no known workaround at this time.
    last seen 2019-02-21
    modified 2018-07-12
    plugin id 72159
    published 2014-01-28
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=72159
    title GLSA-201401-32 : Exim: Multiple vulnerabilities
  • NASL family SuSE Local Security Checks
    NASL id SUSE_11_2_EXIM-101211.NASL
    description remote attackers could trick exim into running arbitrary code (CVE-2010-4344). A privilege escalation flaw allowed attackers to gain root access (CVE-2010-4345).
    last seen 2019-02-21
    modified 2018-11-10
    plugin id 53715
    published 2011-05-05
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=53715
    title openSUSE Security Update : exim (openSUSE-SU-2010:1052-1)
  • NASL family FreeBSD Local Security Checks
    NASL id FREEBSD_PKG_E4FCF020044711E0BECC0022156E8794.NASL
    description David Woodhouse reports : Secondly a privilege escalation where the trusted 'exim' user is able to tell Exim to use arbitrary config files, in which further ${run ...} commands will be invoked as root.
    last seen 2019-02-21
    modified 2018-12-19
    plugin id 51446
    published 2011-01-10
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=51446
    title FreeBSD : exim -- local privilege escalation (e4fcf020-0447-11e0-becc-0022156e8794)
  • NASL family Red Hat Local Security Checks
    NASL id REDHAT-RHSA-2011-0153.NASL
    description Updated exim packages that fix one security issue are now available for Red Hat Enterprise Linux 4 and 5. The Red Hat Security Response Team has rated this update as having moderate security impact. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available from the CVE link in the References section. Exim is a mail transport agent (MTA) developed at the University of Cambridge for use on UNIX systems connected to the Internet. A privilege escalation flaw was discovered in Exim. If an attacker were able to gain access to the 'exim' user, they could cause Exim to execute arbitrary commands as the root user. (CVE-2010-4345) This update adds a new configuration file, '/etc/exim/trusted-configs'. To prevent Exim from running arbitrary commands as root, Exim will now drop privileges when run with a configuration file not listed as trusted. This could break backwards compatibility with some Exim configurations, as the trusted-configs file only trusts '/etc/exim/exim.conf' and '/etc/exim/exim4.conf' by default. If you are using a configuration file not listed in the new trusted-configs file, you will need to add it manually. Additionally, Exim will no longer allow a user to execute exim as root with the -D command line option to override macro definitions. All macro definitions that require root permissions must now reside in a trusted configuration file. Users of Exim are advised to upgrade to these updated packages, which contain a backported patch to correct this issue. After installing this update, the exim daemon will be restarted automatically.
    last seen 2019-02-21
    modified 2019-01-02
    plugin id 51562
    published 2011-01-18
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=51562
    title RHEL 4 / 5 : exim (RHSA-2011:0153)
packetstorm via4
data source https://packetstormsecurity.com/files/download/96605/exim4_string_format.rb.txt
id PACKETSTORM:96605
last seen 2016-12-05
published 2010-12-11
reporter H D Moore
source https://packetstormsecurity.com/files/96605/Exim4-4.69-string_format-Function-Heap-Buffer-Overflow.html
title Exim4 <= 4.69 string_format Function Heap Buffer Overflow
redhat via4
advisories
bugzilla
id 662012
title CVE-2010-4345 exim privilege escalation
oval
OR
  • AND
    • comment Red Hat Enterprise Linux 4 is installed
      oval oval:com.redhat.rhsa:tst:20060016001
    • OR
      • AND
        • comment exim is earlier than 0:4.43-1.RHEL4.5.el4_8.3
          oval oval:com.redhat.rhsa:tst:20110153002
        • comment exim is signed with Red Hat master key
          oval oval:com.redhat.rhsa:tst:20100970003
      • AND
        • comment exim-doc is earlier than 0:4.43-1.RHEL4.5.el4_8.3
          oval oval:com.redhat.rhsa:tst:20110153006
        • comment exim-doc is signed with Red Hat master key
          oval oval:com.redhat.rhsa:tst:20100970007
      • AND
        • comment exim-mon is earlier than 0:4.43-1.RHEL4.5.el4_8.3
          oval oval:com.redhat.rhsa:tst:20110153008
        • comment exim-mon is signed with Red Hat master key
          oval oval:com.redhat.rhsa:tst:20100970005
      • AND
        • comment exim-sa is earlier than 0:4.43-1.RHEL4.5.el4_8.3
          oval oval:com.redhat.rhsa:tst:20110153004
        • comment exim-sa is signed with Red Hat master key
          oval oval:com.redhat.rhsa:tst:20100970009
  • AND
    • comment Red Hat Enterprise Linux 5 is installed
      oval oval:com.redhat.rhsa:tst:20070055001
    • OR
      • AND
        • comment exim is earlier than 0:4.63-5.el5_6.2
          oval oval:com.redhat.rhsa:tst:20110153011
        • comment exim is signed with Red Hat redhatrelease key
          oval oval:com.redhat.rhsa:tst:20100970012
      • AND
        • comment exim-mon is earlier than 0:4.63-5.el5_6.2
          oval oval:com.redhat.rhsa:tst:20110153015
        • comment exim-mon is signed with Red Hat redhatrelease key
          oval oval:com.redhat.rhsa:tst:20100970016
      • AND
        • comment exim-sa is earlier than 0:4.63-5.el5_6.2
          oval oval:com.redhat.rhsa:tst:20110153013
        • comment exim-sa is signed with Red Hat redhatrelease key
          oval oval:com.redhat.rhsa:tst:20100970014
rhsa
id RHSA-2011:0153
released 2011-01-17
severity Moderate
title RHSA-2011:0153: exim security update (Moderate)
rpms
  • exim-0:4.43-1.RHEL4.5.el4_8.3
  • exim-doc-0:4.43-1.RHEL4.5.el4_8.3
  • exim-mon-0:4.43-1.RHEL4.5.el4_8.3
  • exim-sa-0:4.43-1.RHEL4.5.el4_8.3
  • exim-0:4.63-5.el5_6.2
  • exim-mon-0:4.63-5.el5_6.2
  • exim-sa-0:4.63-5.el5_6.2
refmap via4
bid 45341
bugtraq 20101213 Exim security issue in historical release
cert-vn VU#758489
confirm
debian
  • DSA-2131
  • DSA-2154
misc
mlist
  • [exim-dev] 20101207 Remote root vulnerability in Exim
  • [exim-dev] 20101209 Re: [Exim-maintainers] Remote root vulnerability in Exim
  • [exim-dev] 20101210 Re: Remote root vulnerability in Exim
  • [oss-security] 20101210 Exim remote root
sectrack 1024859
secunia
  • 42576
  • 42930
  • 43128
  • 43243
suse SUSE-SA:2010:059
ubuntu USN-1060-1
vupen
  • ADV-2010-3171
  • ADV-2010-3204
  • ADV-2011-0135
  • ADV-2011-0245
  • ADV-2011-0364
Last major update 17-02-2011 - 02:01
Published 14-12-2010 - 11:00
Last modified 10-10-2018 - 16:08
Back to Top