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.
References
Link | Resource |
---|---|
https://groups.google.com/d/msg/golang-dev/RinSE3EiJBI/kYL7zb07AgAJ | Mailing List Vendor Advisory |
https://golang.org/cl/68210 | Vendor Advisory |
https://golang.org/cl/68023 | Issue Tracking Patch Vendor Advisory |
https://github.com/golang/go/issues/22134 | Issue Tracking Patch Vendor Advisory |
http://www.securityfocus.com/bid/101197 | Third Party Advisory VDB Entry |
https://security.gentoo.org/glsa/201710-23 | Third Party Advisory |
https://access.redhat.com/errata/RHSA-2017:3463 | |
https://access.redhat.com/errata/RHSA-2018:0878 |
Configurations
Information
Published : 2017-10-05 14:29
Updated : 2019-10-02 17:03
NVD link : CVE-2017-15042
Mitre link : CVE-2017-15042
JSON object : View
CWE
CWE-319
Cleartext Transmission of Sensitive Information
Products Affected
golang
- go