CVE-2011-1431 json
The STARTTLS implementation in qmail-smtpd.c in qmail-smtpd in the netqmail-1.06-tls patch for netqmail 1.06 does not properly restrict I/O…
published 2011-03-16 15 y ago modified 2026-06-16 4 mo ago also EUVD-2011-1436
- cvss
- 6.8
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 4.6%
- EPSS 4.6% chance of exploitation in 30 days, percentile 91%
- public exploits
- 0
- none known
Summary
The STARTTLS implementation in qmail-smtpd.c in qmail-smtpd in the netqmail-1.06-tls patch for netqmail 1.06 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, related to a "plaintext command injection" attack, a similar issue to CVE-2011-0411.
Patch / fix
Exploit prediction
4.59% chance of exploitation in the next 30 days, higher than 91% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- postfix.org http://www.postfix.org/CVE-2011-0411.html referenced PoC, tagged "exploit" by a source, unverified
- securityfocus.com http://www.securityfocus.com/archive/1/516901 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 6.8 | AV:N/AC:M/Au:N/C:P/I:P/A:P |
References
-
inoa.net
/qmail-tls/vu555316.patch
patch
-
postfix.org
/CVE-2011-0411.html
exploit, vendor-advisory
-
securityfocus.com
/archive/1/516901
mailing-list, exploit
-
vupen.com
/english/advisories/2011/0612
vdb-entry, vendor-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/65932
vdb-entry
-
kb.cert.org
/vuls/id/MAPG-8D9M5Q
us-government-resource
-
securityfocus.com
/bid/46767
vdb-entry
-
kb.cert.org
/vuls/id/555316
third-party-advisory, us-government-resource
-
securityreason.com
/securityalert/8144
third-party-advisory
Sources
- CVE List CVE-2011-1431
- NVD CVE-2011-1431
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.