ID CVE-2011-1720
Summary The SMTP server in Postfix before 2.5.13, 2.6.x before 2.6.10, 2.7.x before 2.7.4, and 2.8.x before 2.8.3, when certain Cyrus SASL authentication methods are enabled, does not create a new server handle after client authentication fails, which allows remote attackers to cause a denial of service (heap memory corruption and daemon crash) or possibly execute arbitrary code via an invalid AUTH command with one method followed by an AUTH command with a different method.
References
Vulnerable Configurations
  • postfix 2.0.0
    cpe:2.3:a:postfix:postfix:2.0.0
  • postfix 2.0.1
    cpe:2.3:a:postfix:postfix:2.0.1
  • postfix 2.0.2
    cpe:2.3:a:postfix:postfix:2.0.2
  • postfix 2.0.3
    cpe:2.3:a:postfix:postfix:2.0.3
  • postfix 2.0.4
    cpe:2.3:a:postfix:postfix:2.0.4
  • postfix 2.0.5
    cpe:2.3:a:postfix:postfix:2.0.5
  • postfix 2.0.6
    cpe:2.3:a:postfix:postfix:2.0.6
  • postfix 2.0.7
    cpe:2.3:a:postfix:postfix:2.0.7
  • postfix 2.0.8
    cpe:2.3:a:postfix:postfix:2.0.8
  • postfix 2.0.9
    cpe:2.3:a:postfix:postfix:2.0.9
  • postfix 2.0.10
    cpe:2.3:a:postfix:postfix:2.0.10
  • postfix 2.0.11
    cpe:2.3:a:postfix:postfix:2.0.11
  • postfix 2.0.12
    cpe:2.3:a:postfix:postfix:2.0.12
  • postfix 2.0.13
    cpe:2.3:a:postfix:postfix:2.0.13
  • postfix 2.0.14
    cpe:2.3:a:postfix:postfix:2.0.14
  • postfix 2.0.15
    cpe:2.3:a:postfix:postfix:2.0.15
  • postfix 2.0.16
    cpe:2.3:a:postfix:postfix:2.0.16
  • postfix 2.0.17
    cpe:2.3:a:postfix:postfix:2.0.17
  • postfix 2.0.18
    cpe:2.3:a:postfix:postfix:2.0.18
  • postfix 2.0.19
    cpe:2.3:a:postfix:postfix:2.0.19
  • postfix 2.1.0
    cpe:2.3:a:postfix:postfix:2.1.0
  • postfix 2.1.1
    cpe:2.3:a:postfix:postfix:2.1.1
  • postfix 2.1.2
    cpe:2.3:a:postfix:postfix:2.1.2
  • postfix 2.1.3
    cpe:2.3:a:postfix:postfix:2.1.3
  • postfix 2.1.4
    cpe:2.3:a:postfix:postfix:2.1.4
  • postfix 2.1.5
    cpe:2.3:a:postfix:postfix:2.1.5
  • postfix 2.1.6
    cpe:2.3:a:postfix:postfix:2.1.6
  • postfix 2.2.0
    cpe:2.3:a:postfix:postfix:2.2.0
  • postfix 2.2.1
    cpe:2.3:a:postfix:postfix:2.2.1
  • postfix 2.2.2
    cpe:2.3:a:postfix:postfix:2.2.2
  • postfix 2.2.3
    cpe:2.3:a:postfix:postfix:2.2.3
  • postfix 2.2.4
    cpe:2.3:a:postfix:postfix:2.2.4
  • postfix 2.2.5
    cpe:2.3:a:postfix:postfix:2.2.5
  • postfix 2.2.6
    cpe:2.3:a:postfix:postfix:2.2.6
  • postfix 2.2.7
    cpe:2.3:a:postfix:postfix:2.2.7
  • postfix 2.2.8
    cpe:2.3:a:postfix:postfix:2.2.8
  • postfix 2.2.9
    cpe:2.3:a:postfix:postfix:2.2.9
  • postfix 2.2.10
    cpe:2.3:a:postfix:postfix:2.2.10
  • postfix 2.2.11
    cpe:2.3:a:postfix:postfix:2.2.11
  • postfix 2.2.12
    cpe:2.3:a:postfix:postfix:2.2.12
  • postfix 2.3
    cpe:2.3:a:postfix:postfix:2.3
  • postfix 2.3.0
    cpe:2.3:a:postfix:postfix:2.3.0
  • postfix 2.3.1
    cpe:2.3:a:postfix:postfix:2.3.1
  • postfix 2.3.2
    cpe:2.3:a:postfix:postfix:2.3.2
  • postfix 2.3.3
    cpe:2.3:a:postfix:postfix:2.3.3
  • postfix 2.3.4
    cpe:2.3:a:postfix:postfix:2.3.4
  • postfix 2.3.5
    cpe:2.3:a:postfix:postfix:2.3.5
  • postfix 2.3.6
    cpe:2.3:a:postfix:postfix:2.3.6
  • postfix 2.3.7
    cpe:2.3:a:postfix:postfix:2.3.7
  • postfix 2.3.8
    cpe:2.3:a:postfix:postfix:2.3.8
  • postfix 2.3.9
    cpe:2.3:a:postfix:postfix:2.3.9
  • postfix 2.3.10
    cpe:2.3:a:postfix:postfix:2.3.10
  • postfix 2.3.11
    cpe:2.3:a:postfix:postfix:2.3.11
  • postfix 2.3.12
    cpe:2.3:a:postfix:postfix:2.3.12
  • postfix 2.3.13
    cpe:2.3:a:postfix:postfix:2.3.13
  • postfix 2.3.14
    cpe:2.3:a:postfix:postfix:2.3.14
  • postfix 2.3.15
    cpe:2.3:a:postfix:postfix:2.3.15
  • postfix 2.3.16
    cpe:2.3:a:postfix:postfix:2.3.16
  • postfix 2.3.17
    cpe:2.3:a:postfix:postfix:2.3.17
  • postfix 2.3.18
    cpe:2.3:a:postfix:postfix:2.3.18
  • postfix 2.3.19
    cpe:2.3:a:postfix:postfix:2.3.19
  • postfix 2.4
    cpe:2.3:a:postfix:postfix:2.4
  • postfix 2.4.0
    cpe:2.3:a:postfix:postfix:2.4.0
  • postfix 2.4.1
    cpe:2.3:a:postfix:postfix:2.4.1
  • postfix 2.4.2
    cpe:2.3:a:postfix:postfix:2.4.2
  • postfix 2.4.3
    cpe:2.3:a:postfix:postfix:2.4.3
  • postfix 2.4.4
    cpe:2.3:a:postfix:postfix:2.4.4
  • postfix 2.4.5
    cpe:2.3:a:postfix:postfix:2.4.5
  • postfix 2.4.6
    cpe:2.3:a:postfix:postfix:2.4.6
  • postfix 2.4.7
    cpe:2.3:a:postfix:postfix:2.4.7
  • postfix 2.4.8
    cpe:2.3:a:postfix:postfix:2.4.8
  • postfix 2.4.9
    cpe:2.3:a:postfix:postfix:2.4.9
  • postfix 2.4.10
    cpe:2.3:a:postfix:postfix:2.4.10
  • postfix 2.4.11
    cpe:2.3:a:postfix:postfix:2.4.11
  • postfix 2.4.12
    cpe:2.3:a:postfix:postfix:2.4.12
  • postfix 2.4.13
    cpe:2.3:a:postfix:postfix:2.4.13
  • postfix 2.4.14
    cpe:2.3:a:postfix:postfix:2.4.14
  • postfix 2.4.15
    cpe:2.3:a:postfix:postfix:2.4.15
  • postfix 2.5.0
    cpe:2.3:a:postfix:postfix:2.5.0
  • postfix 2.5.1
    cpe:2.3:a:postfix:postfix:2.5.1
  • postfix 2.5.2
    cpe:2.3:a:postfix:postfix:2.5.2
  • postfix 2.5.3
    cpe:2.3:a:postfix:postfix:2.5.3
  • postfix 2.5.4
    cpe:2.3:a:postfix:postfix:2.5.4
  • Postfix 2.5.5
    cpe:2.3:a:postfix:postfix:2.5.5
  • Postfix 2.5.6
    cpe:2.3:a:postfix:postfix:2.5.6
  • Postfix 2.5.7
    cpe:2.3:a:postfix:postfix:2.5.7
  • Postfix 2.5.8
    cpe:2.3:a:postfix:postfix:2.5.8
  • Postfix 2.5.9
    cpe:2.3:a:postfix:postfix:2.5.9
  • Postfix 2.5.10
    cpe:2.3:a:postfix:postfix:2.5.10
  • Postfix 2.5.11
    cpe:2.3:a:postfix:postfix:2.5.11
  • Postfix 2.5.12
    cpe:2.3:a:postfix:postfix:2.5.12
  • postfix 2.6
    cpe:2.3:a:postfix:postfix:2.6
  • postfix 2.6.0
    cpe:2.3:a:postfix:postfix:2.6.0
  • postfix 2.6.1
    cpe:2.3:a:postfix:postfix:2.6.1
  • postfix 2.6.2
    cpe:2.3:a:postfix:postfix:2.6.2
  • postfix 2.6.3
    cpe:2.3:a:postfix:postfix:2.6.3
  • postfix 2.6.4
    cpe:2.3:a:postfix:postfix:2.6.4
  • postfix 2.6.5
    cpe:2.3:a:postfix:postfix:2.6.5
  • postfix 2.6.6
    cpe:2.3:a:postfix:postfix:2.6.6
  • postfix 2.6.7
    cpe:2.3:a:postfix:postfix:2.6.7
  • postfix 2.6.8
    cpe:2.3:a:postfix:postfix:2.6.8
  • postfix 2.6.9
    cpe:2.3:a:postfix:postfix:2.6.9
  • postfix 2.7.0
    cpe:2.3:a:postfix:postfix:2.7.0
  • postfix 2.7.1
    cpe:2.3:a:postfix:postfix:2.7.1
  • postfix 2.7.2
    cpe:2.3:a:postfix:postfix:2.7.2
  • postfix 2.7.3
    cpe:2.3:a:postfix:postfix:2.7.3
  • postfix 2.8.0
    cpe:2.3:a:postfix:postfix:2.8.0
  • postfix 2.8.1
    cpe:2.3:a:postfix:postfix:2.8.1
  • postfix 2.8.2
    cpe:2.3:a:postfix:postfix:2.8.2
CVSS
Base: 6.8 (as of 13-05-2011 - 14:47)
Impact:
Exploitability:
CWE CWE-119
CAPEC
  • Buffer Overflow via Environment Variables
    This attack pattern involves causing a buffer overflow through manipulation of environment variables. Once the attacker finds that they can modify an environment variable, they may try to overflow associated buffers. This attack leverages implicit trust often placed in environment variables.
  • Overflow Buffers
    Buffer Overflow attacks target improper or missing bounds checking on buffer operations, typically triggered by input injected by an attacker. As a consequence, an attacker is able to write past the boundaries of allocated buffer regions in memory, causing a program crash or potentially redirection of execution as per the attackers' choice.
  • Client-side Injection-induced Buffer Overflow
    This type of attack exploits a buffer overflow vulnerability in targeted client software through injection of malicious content from a custom-built hostile service.
  • Filter Failure through Buffer Overflow
    In this attack, the idea is to cause an active filter to fail by causing an oversized transaction. An attacker may try to feed overly long input strings to the program in an attempt to overwhelm the filter (by causing a buffer overflow) and hoping that the filter does not fail securely (i.e. the user input is let into the system unfiltered).
  • MIME Conversion
    An attacker exploits a weakness in the MIME conversion routine to cause a buffer overflow and gain control over the mail server machine. The MIME system is designed to allow various different information formats to be interpreted and sent via e-mail. Attack points exist when data are converted to MIME compatible format and back.
  • Overflow Binary Resource File
    An attack of this type exploits a buffer overflow vulnerability in the handling of binary resources. Binary resources may include music files like MP3, image files like JPEG files, and any other binary file. These attacks may pass unnoticed to the client machine through normal usage of files, such as a browser loading a seemingly innocent JPEG file. This can allow the attacker access to the execution stack and execute arbitrary code in the target process. This attack pattern is a variant of standard buffer overflow attacks using an unexpected vector (binary files) to wrap its attack and open up a new attack vector. The attacker is required to either directly serve the binary content to the victim, or place it in a locale like a MP3 sharing application, for the victim to download. The attacker then is notified upon the download or otherwise locates the vulnerability opened up by the buffer overflow.
  • Buffer Overflow via Symbolic Links
    This type of attack leverages the use of symbolic links to cause buffer overflows. An attacker can try to create or manipulate a symbolic link file such that its contents result in out of bounds data. When the target software processes the symbolic link file, it could potentially overflow internal buffers with insufficient bounds checking.
  • Overflow Variables and Tags
    This type of attack leverages the use of tags or variables from a formatted configuration data to cause buffer overflow. The attacker crafts a malicious HTML page or configuration file that includes oversized strings, thus causing an overflow.
  • Buffer Overflow via Parameter Expansion
    In this attack, the target software is given input that the attacker knows will be modified and expanded in size during processing. This attack relies on the target software failing to anticipate that the expanded data may exceed some internal limit, thereby creating a buffer overflow.
  • Buffer Overflow in an API Call
    This attack targets libraries or shared code modules which are vulnerable to buffer overflow attacks. An attacker who has access to an API may try to embed malicious code in the API function call and exploit a buffer overflow vulnerability in the function's implementation. All clients that make use of the code library thus become vulnerable by association. This has a very broad effect on security across a system, usually affecting more than one software process.
  • Buffer Overflow in Local Command-Line Utilities
    This attack targets command-line utilities available in a number of shells. An attacker can leverage a vulnerability found in a command-line utility to escalate privilege to root.
Access
VectorComplexityAuthentication
NETWORK MEDIUM NONE
Impact
ConfidentialityIntegrityAvailability
PARTIAL PARTIAL PARTIAL
nessus via4
  • NASL family SuSE Local Security Checks
    NASL id SUSE_11_2_POSTFIX-110510.NASL
    description Remote attackers could potentially exploit a memory corruption issue in postfix' SASL implementation to execute arbitrary code (CVE-2011-1720).
    last seen 2019-02-21
    modified 2018-11-10
    plugin id 53875
    published 2011-05-12
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=53875
    title openSUSE Security Update : postfix (openSUSE-SU-2011:0476-1)
  • NASL family Debian Local Security Checks
    NASL id DEBIAN_DSA-2233.NASL
    description Several vulnerabilities were discovered in Postfix, a mail transfer agent. The Common Vulnerabilities and Exposures project identifies the following problems : - CVE-2009-2939 The postinst script grants the postfix user write access to /var/spool/postfix/pid, which might allow local users to conduct symlink attacks that overwrite arbitrary files. - CVE-2011-0411 The STARTTLS implementation does not properly restrict I/O buffering, which allows man-in-the-middle attackers to insert commands into encrypted SMTP sessions by sending a cleartext command that is processed after TLS is in place. - CVE-2011-1720 A heap-based read-only buffer overflow allows malicious clients to crash the smtpd server process using a crafted SASL authentication request.
    last seen 2019-02-21
    modified 2018-11-10
    plugin id 53860
    published 2011-05-11
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=53860
    title Debian DSA-2233-1 : postfix - several vulnerabilities
  • NASL family SuSE Local Security Checks
    NASL id SUSE_POSTFIX-7503.NASL
    description Remote attackers could have potentially exploited a memory corruption issue in postfix' SASL implementation to execute arbitrary code (CVE-2011-1720). This has been fixed.
    last seen 2019-02-21
    modified 2012-05-17
    plugin id 53855
    published 2011-05-10
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=53855
    title SuSE 10 Security Update : postfix (ZYPP Patch Number 7503)
  • NASL family Red Hat Local Security Checks
    NASL id REDHAT-RHSA-2011-0843.NASL
    description Updated postfix packages that fix one security issue are now available for Red Hat Enterprise Linux 4, 5, and 6. 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. Postfix is a Mail Transport Agent (MTA), supporting LDAP, SMTP AUTH (SASL), and TLS. A heap-based buffer over-read flaw was found in the way Postfix performed SASL handlers management for SMTP sessions, when Cyrus SASL authentication was enabled. A remote attacker could use this flaw to cause the Postfix smtpd server to crash via a specially crafted SASL authentication request. The smtpd process was automatically restarted by the postfix master process after the time configured with service_throttle_time elapsed. (CVE-2011-1720) Note: Cyrus SASL authentication for Postfix is not enabled by default. Red Hat would like to thank the CERT/CC for reporting this issue. Upstream acknowledges Thomas Jarosch of Intra2net AG as the original reporter. Users of Postfix are advised to upgrade to these updated packages, which contain a backported patch to resolve this issue. After installing this update, the postfix service will be restarted automatically.
    last seen 2019-02-21
    modified 2018-11-26
    plugin id 54931
    published 2011-06-01
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=54931
    title RHEL 4 / 5 / 6 : postfix (RHSA-2011:0843)
  • NASL family SuSE Local Security Checks
    NASL id SUSE_11_4_POSTFIX-110510.NASL
    description Remote attackers could potentially exploit a memory corruption issue in postfix' SASL implementation to execute arbitrary code (CVE-2011-1720).
    last seen 2019-02-21
    modified 2018-11-10
    plugin id 75997
    published 2014-06-13
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=75997
    title openSUSE Security Update : postfix (openSUSE-SU-2011:0476-1)
  • NASL family CentOS Local Security Checks
    NASL id CENTOS_RHSA-2011-0843.NASL
    description Updated postfix packages that fix one security issue are now available for Red Hat Enterprise Linux 4, 5, and 6. 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. Postfix is a Mail Transport Agent (MTA), supporting LDAP, SMTP AUTH (SASL), and TLS. A heap-based buffer over-read flaw was found in the way Postfix performed SASL handlers management for SMTP sessions, when Cyrus SASL authentication was enabled. A remote attacker could use this flaw to cause the Postfix smtpd server to crash via a specially crafted SASL authentication request. The smtpd process was automatically restarted by the postfix master process after the time configured with service_throttle_time elapsed. (CVE-2011-1720) Note: Cyrus SASL authentication for Postfix is not enabled by default. Red Hat would like to thank the CERT/CC for reporting this issue. Upstream acknowledges Thomas Jarosch of Intra2net AG as the original reporter. Users of Postfix are advised to upgrade to these updated packages, which contain a backported patch to resolve this issue. After installing this update, the postfix service will be restarted automatically.
    last seen 2019-02-21
    modified 2018-11-10
    plugin id 54937
    published 2011-06-02
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=54937
    title CentOS 4 / 5 : postfix (CESA-2011:0843)
  • NASL family SuSE Local Security Checks
    NASL id SUSE_POSTFIX-7502.NASL
    description Remote attackers could have potentially exploited a memory corruption issue in postfix' SASL implementation to execute arbitrary code (CVE-2011-1720). This has been fixed.
    last seen 2019-02-21
    modified 2012-05-17
    plugin id 57243
    published 2011-12-13
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=57243
    title SuSE 10 Security Update : postfix (ZYPP Patch Number 7502)
  • NASL family Scientific Linux Local Security Checks
    NASL id SL_20110531_POSTFIX_ON_SL4_X.NASL
    description Postfix is a Mail Transport Agent (MTA), supporting LDAP, SMTP AUTH (SASL), and TLS. A heap-based buffer over-read flaw was found in the way Postfix performed SASL handlers management for SMTP sessions, when Cyrus SASL authentication was enabled. A remote attacker could use this flaw to cause the Postfix smtpd server to crash via a specially crafted SASL authentication request. The smtpd process was automatically restarted by the postfix master process after the time configured with service_throttle_time elapsed. (CVE-2011-1720) Note: Cyrus SASL authentication for Postfix is not enabled by default. Users of Postfix are advised to upgrade to these updated packages, which contain a backported patch to resolve this issue. After installing this update, the postfix service will be restarted automatically.
    last seen 2019-02-21
    modified 2018-12-31
    plugin id 61060
    published 2012-08-01
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=61060
    title Scientific Linux Security Update : postfix on SL4.x, SL5.x i386/x86_64
  • NASL family Oracle Linux Local Security Checks
    NASL id ORACLELINUX_ELSA-2011-0843.NASL
    description From Red Hat Security Advisory 2011:0843 : Updated postfix packages that fix one security issue are now available for Red Hat Enterprise Linux 4, 5, and 6. 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. Postfix is a Mail Transport Agent (MTA), supporting LDAP, SMTP AUTH (SASL), and TLS. A heap-based buffer over-read flaw was found in the way Postfix performed SASL handlers management for SMTP sessions, when Cyrus SASL authentication was enabled. A remote attacker could use this flaw to cause the Postfix smtpd server to crash via a specially crafted SASL authentication request. The smtpd process was automatically restarted by the postfix master process after the time configured with service_throttle_time elapsed. (CVE-2011-1720) Note: Cyrus SASL authentication for Postfix is not enabled by default. Red Hat would like to thank the CERT/CC for reporting this issue. Upstream acknowledges Thomas Jarosch of Intra2net AG as the original reporter. Users of Postfix are advised to upgrade to these updated packages, which contain a backported patch to resolve this issue. After installing this update, the postfix service will be restarted automatically.
    last seen 2019-02-21
    modified 2018-07-18
    plugin id 68283
    published 2013-07-12
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=68283
    title Oracle Linux 4 / 5 / 6 : postfix (ELSA-2011-0843)
  • NASL family SMTP problems
    NASL id POSTFIX_MEMORY_CORRUPTION_EXPLOIT.NASL
    description The Postfix mail server listening on this port appears vulnerable to a memory corruption attack as Nessus was able to crash an SMTP session with this host by using two different authentication methods in one session. Note that code execution as the unprivileged postfix user may also be possible.
    last seen 2019-02-21
    modified 2018-11-15
    plugin id 54584
    published 2011-05-19
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=54584
    title Postfix Cyrus SASL Authentication Context Data Reuse Memory Corruption (exploit)
  • NASL family FreeBSD Local Security Checks
    NASL id FREEBSD_PKG_3EB2C100738B11E089F4001E90D46635.NASL
    description The Postfix SMTP server has a memory corruption error, when the Cyrus SASL library is used with authentication mechanisms other than PLAIN and LOGIN (ANONYMOUS is not affected, but should not be used for other reasons). This memory corruption is known to result in a program crash (SIGSEV).
    last seen 2019-02-21
    modified 2018-11-10
    plugin id 53852
    published 2011-05-10
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=53852
    title FreeBSD : Postfix -- memory corruption vulnerability (3eb2c100-738b-11e0-89f4-001e90d46635)
  • NASL family SMTP problems
    NASL id POSTFIX_MEMORY_CORRUPTION.NASL
    description According to its banner, the version of the Postfix mail server listening on this port is earlier than 2.5.13, 2.6.19, 2.7.4, or 2.8.3. Such versions may be vulnerable to a memory corruption attack if they have Cyrus SASL enabled and are allowing authentication methods other than ANONYMOUS, LOGIN, and PLAIN. Code execution as the unprivileged postfix user may also be possible. Note that Nessus did not test whether the remote server was using Cyrus specifically, as opposed to another SASL library such as Dovecot.
    last seen 2019-02-21
    modified 2018-11-15
    plugin id 54583
    published 2011-05-19
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=54583
    title Postfix Cyrus SASL Authentication Context Data Reuse Memory Corruption
  • NASL family SuSE Local Security Checks
    NASL id SUSE_11_POSTFIX-110504.NASL
    description Remote attackers could have potentially exploited a memory corruption issue in postfix' SASL implementation to execute arbitrary code (CVE-2011-1720). This has been fixed.
    last seen 2019-02-21
    modified 2013-10-25
    plugin id 53854
    published 2011-05-10
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=53854
    title SuSE 11.1 Security Update : postfix (SAT Patch Number 4478)
  • NASL family SuSE Local Security Checks
    NASL id SUSE_11_3_POSTFIX-110510.NASL
    description Remote attackers could potentially exploit a memory corruption issue in postfix' SASL implementation to execute arbitrary code (CVE-2011-1720).
    last seen 2019-02-21
    modified 2018-11-10
    plugin id 75711
    published 2014-06-13
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=75711
    title openSUSE Security Update : postfix (openSUSE-SU-2011:0476-1)
  • NASL family Mandriva Local Security Checks
    NASL id MANDRIVA_MDVSA-2011-090.NASL
    description A vulnerability has been found and corrected in postfix : The SMTP server in Postfix before 2.5.13, 2.6.x before 2.6.10, 2.7.x before 2.7.4, and 2.8.x before 2.8.3, when certain Cyrus SASL authentication methods are enabled, does not create a new server handle after client authentication fails, which allows remote attackers to cause a denial of service (heap memory corruption and daemon crash) or possibly execute arbitrary code via an invalid AUTH command with one method followed by an AUTH command with a different method (CVE-2011-1720). Packages for 2009.0 are provided as of the Extended Maintenance Program. Please visit this link to learn more: http://store.mandriva.com/product_info.php?cPath=149 products_id=490 The updated packages have been patched to correct this issue.
    last seen 2019-02-21
    modified 2018-07-19
    plugin id 54298
    published 2011-05-18
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=54298
    title Mandriva Linux Security Advisory : postfix (MDVSA-2011:090)
  • NASL family Ubuntu Local Security Checks
    NASL id UBUNTU_USN-1131-1.NASL
    description Thomas Jarosch discovered that Postfix incorrectly handled authentication mechanisms other than PLAIN and LOGIN when the Cyrus SASL library is used. A remote attacker could use this to cause Postfix to crash, leading to a denial of service, or possibly execute arbitrary code as the postfix user. 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 55092
    published 2011-06-13
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=55092
    title Ubuntu 6.06 LTS / 8.04 LTS / 10.04 LTS / 10.10 / 11.04 : postfix vulnerability (USN-1131-1)
  • NASL family SuSE Local Security Checks
    NASL id SUSE9_12707.NASL
    description The following bugs have been fixed : - Remote attackers could potentially exploit a memory corruption issue in postfix' SASL implementation to execute arbitrary code. (CVE-2011-1720) - Also Postfix did not clear the receive buffer after the STARTTLS command. A man-in-the middle could therefore inject commands in the unencrypted stream that get interpreted in the encrypted phase after STARTTLS. (CVE-2011-0411)
    last seen 2019-02-21
    modified 2012-06-14
    plugin id 53868
    published 2011-05-11
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=53868
    title SuSE9 Security Update : Postfix (YOU Patch Number 12707)
  • NASL family Gentoo Local Security Checks
    NASL id GENTOO_GLSA-201206-33.NASL
    description The remote host is affected by the vulnerability described in GLSA-201206-33 (Postfix: Multiple vulnerabilities) A vulnerability have been discovered in Postfix. Please review the CVE identifier referenced below for details. Impact : An attacker could perform a man-in-the-middle attack and inject SMTP commands during the plaintext to TLS session switch or might execute arbitrary code. Workaround : There is no known workaround at this time.
    last seen 2019-02-21
    modified 2018-07-11
    plugin id 59706
    published 2012-06-26
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=59706
    title GLSA-201206-33 : Postfix: Multiple vulnerabilities
redhat via4
advisories
bugzilla
id 699035
title CVE-2011-1720 postfix (smtpd): Crash due to improper management of SASL handlers for SMTP sessions
oval
OR
  • AND
    • comment Red Hat Enterprise Linux 4 is installed
      oval oval:com.redhat.rhba:tst:20070304001
    • OR
      • AND
        • comment postfix is earlier than 2:2.2.10-1.5.el4
          oval oval:com.redhat.rhsa:tst:20110843002
        • comment postfix is signed with Red Hat master key
          oval oval:com.redhat.rhsa:tst:20080839003
      • AND
        • comment postfix-pflogsumm is earlier than 2:2.2.10-1.5.el4
          oval oval:com.redhat.rhsa:tst:20110843004
        • comment postfix-pflogsumm is signed with Red Hat master key
          oval oval:com.redhat.rhsa:tst:20080839007
  • AND
    • comment Red Hat Enterprise Linux 5 is installed
      oval oval:com.redhat.rhba:tst:20070331001
    • OR
      • AND
        • comment postfix is earlier than 2:2.3.3-2.3.el5_6
          oval oval:com.redhat.rhsa:tst:20110843007
        • comment postfix is signed with Red Hat redhatrelease key
          oval oval:com.redhat.rhsa:tst:20080839010
      • AND
        • comment postfix-pflogsumm is earlier than 2:2.3.3-2.3.el5_6
          oval oval:com.redhat.rhsa:tst:20110843009
        • comment postfix-pflogsumm is signed with Red Hat redhatrelease key
          oval oval:com.redhat.rhsa:tst:20080839012
  • AND
    • OR
      • comment Red Hat Enterprise Linux 6 Client is installed
        oval oval:com.redhat.rhba:tst:20111656001
      • comment Red Hat Enterprise Linux 6 Server is installed
        oval oval:com.redhat.rhba:tst:20111656002
      • comment Red Hat Enterprise Linux 6 Workstation is installed
        oval oval:com.redhat.rhba:tst:20111656003
      • comment Red Hat Enterprise Linux 6 ComputeNode is installed
        oval oval:com.redhat.rhba:tst:20111656004
    • OR
      • AND
        • comment postfix is earlier than 2:2.6.6-2.2.el6_1
          oval oval:com.redhat.rhsa:tst:20110843015
        • comment postfix is signed with Red Hat redhatrelease2 key
          oval oval:com.redhat.rhsa:tst:20110423006
      • AND
        • comment postfix-perl-scripts is earlier than 2:2.6.6-2.2.el6_1
          oval oval:com.redhat.rhsa:tst:20110843017
        • comment postfix-perl-scripts is signed with Red Hat redhatrelease2 key
          oval oval:com.redhat.rhsa:tst:20110423008
rhsa
id RHSA-2011:0843
released 2011-05-31
severity Moderate
title RHSA-2011:0843: postfix security update (Moderate)
rpms
  • postfix-2:2.2.10-1.5.el4
  • postfix-pflogsumm-2:2.2.10-1.5.el4
  • postfix-2:2.3.3-2.3.el5_6
  • postfix-pflogsumm-2:2.3.3-2.3.el5_6
  • postfix-2:2.6.6-2.2.el6_1
  • postfix-perl-scripts-2:2.6.6-2.2.el6_1
refmap via4
bid 47778
bugtraq 20110509 Memory corruption in Postfix SMTP server Cyrus SASL support (CVE-2011-1720)
cert-vn VU#727230
confirm
debian DSA-2233
gentoo GLSA-201206-33
mandriva MDVSA-2011:090
mlist [postfix-announce] 20110509 Memory corruption in Postfix SMTP server Cyrus SASL support (CVE-2011-1720)
osvdb 72259
sectrack 1025521
secunia 44500
sreason 8247
suse SUSE-SA:2011:023
ubuntu USN-1131-1
xf postfix-cyrus-sasl-code-exec(67359)
Last major update 07-12-2016 - 22:01
Published 13-05-2011 - 13:05
Last modified 09-10-2018 - 15:31
Back to Top