Homepage

Cleartext Transmission of Sensitive Information Affecting golang-bin package, versions <0:1.8.4-1.41.amzn1

Severity

 Recommended
0.0
medium
0
10

Based on Amazon Linux security rating.

Threat Intelligence

EPSS
0.29% (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-AMZN201803-GOLANGBIN-1708927
  • published27 Sept 2021
  • disclosed5 Oct 2017
Report a new vulnerability Found a mistake?

Introduced: 5 Oct 2017

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

How to fix?

Upgrade Amazon-Linux:2018.03 golang-bin to version 0:1.8.4-1.41.amzn1 or higher.
This issue was patched in ALAS-2017-918.

NVD Description

Note: Versions mentioned in the description apply only to the upstream golang-bin package and not the golang-bin package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 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.