Homepage

Cleartext Transmission of Sensitive Information Affecting go package, versions <1.8.4-r0

Severity

 Recommended
0.0
medium
0
10

CVSS assessment by Snyk's Security Team. Learn more

Threat Intelligence

EPSS
1.28% (70th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-ALPINE36-GO-467740
  • published22 Sept 2019
  • disclosed22 Sept 2019
  • creditUnknown
Report a new vulnerability Found a mistake?

Introduced: 22 Sep 2019

CVE-2017-15042  (opens in a new tab)
CWE-319  (opens in a new tab)

How to fix?

Upgrade Alpine:3.6 go to version 1.8.4-r0 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream go package and not the go package as distributed by Alpine. See How to fix? for Alpine:3.6 relevant fixed versions and status.

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.