CVE-2017-15042

N/A
Published: October 5, 2017 at 09:00 PM UTC
Updated: June 17, 2026 at 01:07 AM UTC
1 product affected across 1 vendorGo

Using N/A by N/A?

Get instant alerts when new vulnerabilities affect N/A - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 1%

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v ≤ 1.8.31.9

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

References (8)

VDB Entryx_refsource_BIDThird Party Advisory
http://www.securityfocus.com/bid/101197
x_refsource_CONFIRMIssue TrackingPatchVendor Advisory
https://github.com/golang/go/issues/22134
x_refsource_CONFIRMIssue TrackingPatchVendor Advisory
https://golang.org/cl/68023
x_refsource_CONFIRMVendor Advisory
https://golang.org/cl/68210
Vendor Advisoryx_refsource_GENTOOThird Party Advisory
https://security.gentoo.org/glsa/201710-23

CVSS

Confidentiality
PARTIAL
Integrity
NONE
Availability
NONE
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-319

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card