Skip to content
Noroxi
CVE-2017-15042· NVD / CVE Program· CNA mitre

An unintended cleartext issue exists in Go before 1.8.4 and 1.9.x before 1.9.1.

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.

MediumCVSS 5.9 · v3.0—No exploit Fix available
Published
Oct 5, 2017
Updated
Jun 16, 2026
EPSS
1.1% · 64th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

23

Monitor

Low priority for now.

CVSS
23 / 40 · 5.9 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 1.1%

Affected systems

VendorProduct
golanggo

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • golang goup to 1.8.3 inclusive
  • golang go1.9

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Gostdlibfrom 1.1.0-0 · before 1.8.41.8.4
Gostdlibfrom 1.9.0-0 · before 1.9.11.9.1
openSUSE:Tumbleweedgobefore 1.17-1.11.17-1.1
openSUSE:Tumbleweedgo1.10before 1.10.8-8.21.10.8-8.2
openSUSE:Tumbleweedgo1.11before 1.11.13-10.51.11.13-10.5
openSUSE:Tumbleweedgo1.12before 1.12.17-4.81.12.17-4.8
openSUSE:Tumbleweedgo1.4before 1.4.3-12.21.4.3-12.2
openSUSE:Tumbleweedgo1.9before 1.9.7-11.21.9.7-11.2
Red Hat:devtools:2::el7go-toolset-7before 0:1.8-10.el70:1.8-10.el7
Red Hat:devtools:2::el7go-toolset-7-buildbefore 0:1.8-10.el70:1.8-10.el7
Red Hat:devtools:2::el7go-toolset-7-dockerfilesbefore 0:1.8-10.el70:1.8-10.el7
Red Hat:devtools:2::el7go-toolset-7-golangbefore 0:1.8.5-1.el70:1.8.5-1.el7
Red Hat:devtools:2::el7go-toolset-7-golang-binbefore 0:1.8.5-1.el70:1.8.5-1.el7
Red Hat:devtools:2::el7go-toolset-7-golang-docsbefore 0:1.8.5-1.el70:1.8.5-1.el7
Red Hat:devtools:2::el7go-toolset-7-golang-miscbefore 0:1.8.5-1.el70:1.8.5-1.el7
Red Hat:devtools:2::el7go-toolset-7-golang-racebefore 0:1.8.5-1.el70:1.8.5-1.el7
Red Hat:devtools:2::el7go-toolset-7-golang-srcbefore 0:1.8.5-1.el70:1.8.5-1.el7
Red Hat:devtools:2::el7go-toolset-7-golang-testsbefore 0:1.8.5-1.el70:1.8.5-1.el7
Red Hat:devtools:2::el7go-toolset-7-runtimebefore 0:1.8-10.el70:1.8-10.el7
Red Hat:devtools:2::el7go-toolset-7-scldevelbefore 0:1.8-10.el70:1.8-10.el7
Red Hat:enterprise_linux:7::servergolangbefore 0:1.9.4-1.el70:1.9.4-1.el7
Red Hat:enterprise_linux:7::servergolang-binbefore 0:1.9.4-1.el70:1.9.4-1.el7
Red Hat:enterprise_linux:7::servergolang-docsbefore 0:1.9.4-1.el70:1.9.4-1.el7
Red Hat:enterprise_linux:7::servergolang-miscbefore 0:1.9.4-1.el70:1.9.4-1.el7

+2

Other highest-scoring records for the same primary product.

  • CVE-2018-7187The "go get" implementation in Go 1.9.4, when the -insecure command-line option is used, does not validate the import path (get/vcs.go only
    54Plan
  • CVE-2018-16873In Go before 1.10.6 and 1.11.x before 1.11.3, the "go get" command is vulnerable to remote code execution when executed with the -u flag and
    52Plan
  • CVE-2021-38297Go before 1.16.9 and 1.17.x before 1.17.2 has a Buffer Overflow via large arguments in a function invocation from a WASM module, when GOARCH
    42Plan
  • CVE-2019-14809net/url in Go before 1.11.13 and 1.12.x before 1.12.8 mishandles malformed hosts in URLs, leading to an authorization bypass in some applica
    42Plan
  • CVE-2015-5739The net/http library in net/textproto/reader.go in Go before 1.4.3 does not properly parse HTTP header keys, which allows remote attackers t
    42Plan
  • CVE-2017-15041Go before 1.8.4 and 1.9.x before 1.9.1 allows "go get" remote command execution.
    42Plan

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Go:stdlib1.8.4Package registry (OSV)
Go:stdlib1.9.1Package registry (OSV)
opensuse:go1.17-1.1 · openSUSE:TumbleweedPackage registry (OSV)
opensuse:go1.101.10.8-8.2 · openSUSE:TumbleweedPackage registry (OSV)
opensuse:go1.111.11.13-10.5 · openSUSE:TumbleweedPackage registry (OSV)
opensuse:go1.121.12.17-4.8 · openSUSE:TumbleweedPackage registry (OSV)
opensuse:go1.41.4.3-12.2 · openSUSE:TumbleweedPackage registry (OSV)
opensuse:go1.91.9.7-11.2 · openSUSE:TumbleweedPackage registry (OSV)
red hat:go-toolset-70:1.8-10.el7 · Red Hat:devtools:2::el7Package registry (OSV)
red hat:go-toolset-7-build0:1.8-10.el7 · Red Hat:devtools:2::el7Package registry (OSV)
red hat:go-toolset-7-dockerfiles0:1.8-10.el7 · Red Hat:devtools:2::el7Package registry (OSV)
red hat:go-toolset-7-golang0:1.8.5-1.el7 · Red Hat:devtools:2::el7Package registry (OSV)
red hat:go-toolset-7-golang-bin0:1.8.5-1.el7 · Red Hat:devtools:2::el7Package registry (OSV)
red hat:go-toolset-7-golang-docs0:1.8.5-1.el7 · Red Hat:devtools:2::el7Package registry (OSV)
red hat:go-toolset-7-golang-misc0:1.8.5-1.el7 · Red Hat:devtools:2::el7Package registry (OSV)
red hat:go-toolset-7-golang-race0:1.8.5-1.el7 · Red Hat:devtools:2::el7Package registry (OSV)
red hat:go-toolset-7-golang-src0:1.8.5-1.el7 · Red Hat:devtools:2::el7Package registry (OSV)
red hat:go-toolset-7-golang-tests0:1.8.5-1.el7 · Red Hat:devtools:2::el7Package registry (OSV)
red hat:go-toolset-7-runtime0:1.8-10.el7 · Red Hat:devtools:2::el7Package registry (OSV)
red hat:go-toolset-7-scldevel0:1.8-10.el7 · Red Hat:devtools:2::el7Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
high · data can be read
Integrity
none
Availability
none
Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
None
Availability impact
None

CVSS vector

CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

nvd-primary

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records