Man-in-the-Middle (MitM) Affecting golang-src package, versions *
Threat Intelligence
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 ID SNYK-RHEL7-GOLANGSRC-5011699
- published 26 Jul 2021
- disclosed 4 Oct 2017
Introduced: 4 Oct 2017
CVE-2017-15042 Open this link in a new tabHow to fix?
There is no fixed version for RHEL:7 golang-src.
NVD Description
Note: Versions mentioned in the description apply only to the upstream golang-src package and not the golang-src package as distributed by RHEL.
See How to fix? for RHEL:7 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.
References
- http://www.securityfocus.com/bid/101197
- 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
- https://access.redhat.com/security/cve/CVE-2017-15042
- https://security.gentoo.org/glsa/201710-23
- https://access.redhat.com/errata/RHSA-2017:3463
- https://access.redhat.com/errata/RHSA-2018:0878