CVE-2017-15042 describes an unintended cleartext issue in Go versions before 1.8.4 and 1.9.1, specifically within the smtp.PlainAuth implementation. This vulnerability allows a man-in-the-middle attacker to intercept usernames and passwords if a malicious SMTP server advertises PLAIN authentication without STARTTLS. Rated Medium severity (CVSS 5.9), it requires high attack complexity and can lead to full confidentiality compromise. There is no evidence of active exploitation, public exploit code, or significant community discussion surrounding this vulnerability.
| Vendor | Product | Version(s) | CPE |
|---|---|---|---|
<= 1.8.3CPE matchmatch criteria | cpe:2.3:a:golang:go:*:*:*:*:*:*:*:* | ||
1.9CPE matchmatch criteria | cpe:2.3:a:golang:go:1.9:*:*:*:*:*:*:* |
CVSS version used by this source: 3.0
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
The average CVE in this peer group has 0.0 Twitter, 0.0 Reddit, 0.0 Bluesky, 0.0 Mastodon, and 0.2 GitHub mentions.
No media coverage found for this CVE.
The average CVE in this peer group has 0.0 InfoSec Media, 0.0 Vendor Blog, and 0.0 Security Researcher mentions.
An unintended cleartext issue exists in Go before 1.8.4 and 1.9.x before 1.9.1. RFC 4954 requires that, during SMTP, the PLAIN auth scheme must only be used on network connections secured with TLS. The original implementation of smtp.PlainAuth in Go 1.0 enforced this requirement, and it was documented to do so. In 2013, upstream issue #5184, this was changed so that the server may decide whether PLAIN is acceptable. The result is that if you set up a man-in-the-middle SMTP server that doesn't advertise STARTTLS and does advertise that PLAIN auth is OK, the smtp.PlainAuth implementation sends the username and password.
Oct 10, 2017golang: smtp.PlainAuth susceptible to man-in-the-middle password harvesting
Oct 4, 2017