First published: Thu Oct 05 2017(Updated: )
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.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
redhat/golang | <1.8.4 | 1.8.4 |
redhat/golang | <1.9.1 | 1.9.1 |
Golang | <=1.8.3 | |
Golang | =1.9 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2017-15042 has a medium severity rating due to potential exposure of plaintext credentials.
To fix CVE-2017-15042, upgrade to Go version 1.8.4 or 1.9.1 or later.
CVE-2017-15042 affects Go versions prior to 1.8.4 and 1.9.x prior to 1.9.1.
The impact of CVE-2017-15042 is that it allows sensitive user credentials to be transmitted in cleartext over SMTP connections.
CVE-2017-15042 is a cleartext credential exposure vulnerability that violates RFC 4954 requirements for SMTP PLAIN authentication.