CVE-2011-1720: Buffer Overflow

Published Apr 22, 2011
·
Updated

A heap-based buffer overread flaw was found in the way Postfix mail transport agent performed SASL handlers management for SMTP sessions, when the Cyrus SASL authentication was enabled. A remote attacker could use this flaw to cause Postfix smtpd server crash via specially-crafted SASL authentication request.

Note: The default configuration of Postfix mail transport agent, as shipped with Red Hat Enterprise Linux 4, 5, and 6 do not enable SASL support for SMTP authentication for mail clients (thus Postfix server instances using it are not vulnerable to this flaw).

Workaround: If your Postfix server configuration contains directive like:

smtpdsaslauthenable = yes

change 'yes' to 'no' or comment the whole line out not to be vulnerable to this flaw.

Other sources

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.

Affected Software

112 affected componentsFixes available
redhat/postfix<2:2.2.10-1.5.el4
2:2.2.10-1.5.el4
redhat/postfix<2:2.3.3-2.3.el5_6
2:2.3.3-2.3.el5_6
redhat/postfix<2:2.6.6-2.2.el6_1
2:2.6.6-2.2.el6_1
Postfix Postfix=2.0.0
Postfix Postfix=2.0.1
Postfix Postfix=2.0.2
Postfix Postfix=2.0.3
Postfix Postfix=2.0.4
Postfix Postfix=2.0.5
Postfix Postfix=2.0.6
Postfix Postfix=2.0.7
Postfix Postfix=2.0.8
Postfix Postfix=2.0.9
Postfix Postfix=2.0.10
Postfix Postfix=2.0.11
Postfix Postfix=2.0.12
Postfix Postfix=2.0.13
Postfix Postfix=2.0.14
Postfix Postfix=2.0.15
Postfix Postfix=2.0.16
Postfix Postfix=2.0.17
Postfix Postfix=2.0.18
Postfix Postfix=2.0.19
Postfix Postfix=2.1.0
Postfix Postfix=2.1.1
Postfix Postfix=2.1.2
Postfix Postfix=2.1.3
Postfix Postfix=2.1.4
Postfix Postfix=2.1.5
Postfix Postfix=2.1.6
Postfix Postfix=2.2.0
Postfix Postfix=2.2.1
Postfix Postfix=2.2.2
Postfix Postfix=2.2.3
Postfix Postfix=2.2.4
Postfix Postfix=2.2.5
Postfix Postfix=2.2.6
Postfix Postfix=2.2.7
Postfix Postfix=2.2.8
Postfix Postfix=2.2.9
Postfix Postfix=2.2.10
Postfix Postfix=2.2.11
Postfix Postfix=2.2.12
Postfix Postfix=2.3
Postfix Postfix=2.3.0
Postfix Postfix=2.3.1
Postfix Postfix=2.3.2
Postfix Postfix=2.3.3
Postfix Postfix=2.3.4
Postfix Postfix=2.3.5
Postfix Postfix=2.3.6
Postfix Postfix=2.3.7
Postfix Postfix=2.3.8
Postfix Postfix=2.3.9
Postfix Postfix=2.3.10
Postfix Postfix=2.3.11
Postfix Postfix=2.3.12
Postfix Postfix=2.3.13
Postfix Postfix=2.3.14
Postfix Postfix=2.3.15
Postfix Postfix=2.3.16
Postfix Postfix=2.3.17
Postfix Postfix=2.3.18
Postfix Postfix=2.3.19
Postfix Postfix=2.4
Postfix Postfix=2.4.0
Postfix Postfix=2.4.1
Postfix Postfix=2.4.2
Postfix Postfix=2.4.3
Postfix Postfix=2.4.4
Postfix Postfix=2.4.5
Postfix Postfix=2.4.6
Postfix Postfix=2.4.7
Postfix Postfix=2.4.8
Postfix Postfix=2.4.9
Postfix Postfix=2.4.10
Postfix Postfix=2.4.11
Postfix Postfix=2.4.12
Postfix Postfix=2.4.13
Postfix Postfix=2.4.14
Postfix Postfix=2.4.15
Postfix Postfix=2.5.0
Postfix Postfix=2.5.1
Postfix Postfix=2.5.2
Postfix Postfix=2.5.3
Postfix Postfix=2.5.4
Postfix Postfix=2.5.5
Postfix Postfix=2.5.6
Postfix Postfix=2.5.7
Postfix Postfix=2.5.8
Postfix Postfix=2.5.9
Postfix Postfix=2.5.10
Postfix Postfix=2.5.11
Postfix Postfix=2.5.12
Postfix Postfix=2.6
Postfix Postfix=2.6.0
Postfix Postfix=2.6.1
Postfix Postfix=2.6.2
Postfix Postfix=2.6.3
Postfix Postfix=2.6.4
Postfix Postfix=2.6.5
Postfix Postfix=2.6.6
Postfix Postfix=2.6.7
Postfix Postfix=2.6.8
Postfix Postfix=2.6.9
Postfix Postfix=2.7.0
Postfix Postfix=2.7.1
Postfix Postfix=2.7.2
Postfix Postfix=2.7.3
Postfix Postfix=2.8.0
Postfix Postfix=2.8.1
Postfix Postfix=2.8.2

Remediation

Event History

Apr 22, 2011
Data Sourced
06:27 PM
DescriptionSeverityAffected Software
May 9, 2011
CVE Published
12:00 AM
May 13, 2011
CVE Published
via MITRE·05:00 PM
Data Sourced
via MITRE·05:00 PM
Description

Parent advisories

This vulnerability appears in the following advisories.

Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2011-1720?

CVE-2011-1720 is considered a medium severity vulnerability due to the potential for remote attackers to crash the Postfix server.

2

How do I fix CVE-2011-1720?

To mitigate CVE-2011-1720, upgrade Postfix to a version higher than 2.2.10-1.5.el4, 2.3.3-2.3.el5_6, or 2.6.6-2.2.el6_1.

3

Who is affected by CVE-2011-1720?

CVE-2011-1720 affects Postfix mail transport agent versions including those mentioned in Red Hat's announcements.

4

What types of attacks can exploit CVE-2011-1720?

CVE-2011-1720 can be exploited by a remote attacker sending specially crafted SASL authentication data, leading to a server crash.

5

Is there a patch available for CVE-2011-1720?

Yes, patches for CVE-2011-1720 are available in the newer versions of Postfix as indicated in the vulnerability announcement.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203