| Name | CVE-2017-15042 |
| Description | 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. |
| Source | CVE (at NVD; CERT, LWN, oss-sec, fulldisc, Red Hat, Ubuntu, Gentoo, SUSE bugzilla/CVE, GitHub advisories/code/issues, web search, more) |
Vulnerable and fixed packages
The table below lists information on source packages.
| Source Package | Release | Version | Status |
|---|
| golang (PTS) | jessie, jessie (lts) | 2:1.3.3-1+deb8u5 | vulnerable |
| golang-1.7 (PTS) | stretch (security), stretch (lts), stretch | 1.7.4-2+deb9u5 | vulnerable |
| golang-1.8 (PTS) | stretch (security), stretch (lts), stretch | 1.8.1-1+deb9u5 | vulnerable |
The information below is based on the following data on fixed versions.
| Package | Type | Release | Fixed Version | Urgency | Origin | Debian Bugs |
|---|
| golang | source | wheezy | (not affected) | | | |
| golang | source | (unstable) | (unfixed) | | | |
| golang-1.7 | source | (unstable) | (unfixed) | | | |
| golang-1.8 | source | (unstable) | 1.8.4-1 | | | |
| golang-1.9 | source | (unstable) | 1.9.1-1 | | | |
Notes
[stretch] - golang-1.8 <ignored> (Minor issue, would require rebuilds of affected go-based packages)
[stretch] - golang-1.7 <ignored> (Minor issue, would require rebuilds of affected go-based packages)
[jessie] - golang <ignored> (Minor issue, would require rebuilds of affected go packages in oldstable)
[wheezy] - golang <not-affected> (Vulnerable code introduced later in version 1.1)
https://github.com/golang/go/issues/22134
https://golang.org/cl/68023
https://golang.org/cl/68210
https://groups.google.com/d/msg/golang-dev/RinSE3EiJBI/kYL7zb07AgAJ