Vulnerability-Lookup

ubuntu-cve-2017-15042

Vulnerability from osv_ubuntu

Published

2017-10-05 21:29

Modified

2025-10-24 04:46

Summary

Details

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.

Severity

5.9 (Medium)


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

N/A (UNKNOWN)

low

References

URL

Type

	https://ubuntu.com/security/CVE-2017-15042	REPORT
	https://github.com/golang/go/issues/22134	REPORT
	https://golang.org/cl/68023	REPORT
	https://golang.org/cl/68210	REPORT
	https://groups.google.com/d/msg/golang-dev/RinSE3…	REPORT
	https://www.cve.org/CVERecord?id=CVE-2017-15042	REPORT

JSON

To clipboard

{
  "affected": [
    {
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "golang-1.6",
            "binary_version": "1.6.2-0ubuntu5~16.04.4"
          },
          {
            "binary_name": "golang-1.6-go",
            "binary_version": "1.6.2-0ubuntu5~16.04.4"
          },
          {
            "binary_name": "golang-1.6-src",
            "binary_version": "1.6.2-0ubuntu5~16.04.4"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:16.04:LTS",
        "name": "golang-1.6",
        "purl": "pkg:deb/ubuntu/golang-1.6@1.6.2-0ubuntu5~16.04.4?arch=source\u0026distro=xenial"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "1.6-0ubuntu1",
        "1.6-0ubuntu2",
        "1.6-0ubuntu3",
        "1.6-0ubuntu4",
        "1.6-0ubuntu5",
        "1.6.1-0ubuntu1",
        "1.6.2-0ubuntu5~16.04",
        "1.6.2-0ubuntu5~16.04.2",
        "1.6.2-0ubuntu5~16.04.3",
        "1.6.2-0ubuntu5~16.04.4"
      ]
    },
    {
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "golang-1.8",
            "binary_version": "1.8.3-2ubuntu1.18.04.1"
          },
          {
            "binary_name": "golang-1.8-go",
            "binary_version": "1.8.3-2ubuntu1.18.04.1"
          },
          {
            "binary_name": "golang-1.8-go-shared-dev",
            "binary_version": "1.8.3-2ubuntu1.18.04.1"
          },
          {
            "binary_name": "golang-1.8-src",
            "binary_version": "1.8.3-2ubuntu1.18.04.1"
          },
          {
            "binary_name": "libgolang-1.8-std1",
            "binary_version": "1.8.3-2ubuntu1.18.04.1"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:18.04:LTS",
        "name": "golang-1.8",
        "purl": "pkg:deb/ubuntu/golang-1.8@1.8.3-2ubuntu1.18.04.1?arch=source\u0026distro=bionic"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "1.8.3-2ubuntu1",
        "1.8.3-2ubuntu1.18.04.1"
      ]
    }
  ],
  "aliases": [],
  "details": "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\u0027t advertise STARTTLS and does advertise that PLAIN auth is OK, the smtp.PlainAuth implementation sends the username and password.",
  "id": "UBUNTU-CVE-2017-15042",
  "modified": "2025-10-24T04:46:32Z",
  "published": "2017-10-05T21:29:00Z",
  "references": [
    {
      "type": "REPORT",
      "url": "https://ubuntu.com/security/CVE-2017-15042"
    },
    {
      "type": "REPORT",
      "url": "https://github.com/golang/go/issues/22134"
    },
    {
      "type": "REPORT",
      "url": "https://golang.org/cl/68023"
    },
    {
      "type": "REPORT",
      "url": "https://golang.org/cl/68210"
    },
    {
      "type": "REPORT",
      "url": "https://groups.google.com/d/msg/golang-dev/RinSE3EiJBI/kYL7zb07AgAJ"
    },
    {
      "type": "REPORT",
      "url": "https://www.cve.org/CVERecord?id=CVE-2017-15042"
    }
  ],
  "related": [],
  "schema_version": "1.7.0",
  "severity": [
    {
      "score": "CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N",
      "type": "CVSS_V3"
    },
    {
      "score": "low",
      "type": "Ubuntu"
    }
  ],
  "upstream": [
    "CVE-2017-15042"
  ]
}

CVE-2017-15042 (GCVE-0-2017-15042)

Vulnerability from cvelistv5 – Published: 2017-10-05 21:00 – Updated: 2024-08-05 19:42

Summary

Severity

No CVSS data available.

CWE

Assigner

mitre mitre root

References

8 references

URL	Tags
https://access.redhat.com/errata/RHSA-2017:3463	vendor-advisoryx_refsource_REDHAT
https://access.redhat.com/errata/RHSA-2018:0878	vendor-advisoryx_refsource_REDHAT
http://www.securityfocus.com/bid/101197	vdb-entryx_refsource_BID
https://golang.org/cl/68210	x_refsource_CONFIRM
https://golang.org/cl/68023	x_refsource_CONFIRM
https://github.com/golang/go/issues/22134	x_refsource_CONFIRM
https://security.gentoo.org/glsa/201710-23	vendor-advisoryx_refsource_GENTOO
https://groups.google.com/d/msg/golang-dev/RinSE3…	x_refsource_CONFIRM

Date Public

2017-10-05 00:00

Show details on NVD website

JSON

To clipboard

{
  "containers": {
    "adp": [
      {
        "providerMetadata": {
          "dateUpdated": "2024-08-05T19:42:22.302Z",
          "orgId": "af854a3a-2127-422b-91ae-364da2661108",
          "shortName": "CVE"
        },
        "references": [
          {
            "name": "RHSA-2017:3463",
            "tags": [
              "vendor-advisory",
              "x_refsource_REDHAT",
              "x_transferred"
            ],
            "url": "https://access.redhat.com/errata/RHSA-2017:3463"
          },
          {
            "name": "RHSA-2018:0878",
            "tags": [
              "vendor-advisory",
              "x_refsource_REDHAT",
              "x_transferred"
            ],
            "url": "https://access.redhat.com/errata/RHSA-2018:0878"
          },
          {
            "name": "101197",
            "tags": [
              "vdb-entry",
              "x_refsource_BID",
              "x_transferred"
            ],
            "url": "http://www.securityfocus.com/bid/101197"
          },
          {
            "tags": [
              "x_refsource_CONFIRM",
              "x_transferred"
            ],
            "url": "https://golang.org/cl/68210"
          },
          {
            "tags": [
              "x_refsource_CONFIRM",
              "x_transferred"
            ],
            "url": "https://golang.org/cl/68023"
          },
          {
            "tags": [
              "x_refsource_CONFIRM",
              "x_transferred"
            ],
            "url": "https://github.com/golang/go/issues/22134"
          },
          {
            "name": "GLSA-201710-23",
            "tags": [
              "vendor-advisory",
              "x_refsource_GENTOO",
              "x_transferred"
            ],
            "url": "https://security.gentoo.org/glsa/201710-23"
          },
          {
            "tags": [
              "x_refsource_CONFIRM",
              "x_transferred"
            ],
            "url": "https://groups.google.com/d/msg/golang-dev/RinSE3EiJBI/kYL7zb07AgAJ"
          }
        ],
        "title": "CVE Program Container"
      }
    ],
    "cna": {
      "affected": [
        {
          "product": "n/a",
          "vendor": "n/a",
          "versions": [
            {
              "status": "affected",
              "version": "n/a"
            }
          ]
        }
      ],
      "datePublic": "2017-10-05T00:00:00.000Z",
      "descriptions": [
        {
          "lang": "en",
          "value": "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\u0027t advertise STARTTLS and does advertise that PLAIN auth is OK, the smtp.PlainAuth implementation sends the username and password."
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "description": "n/a",
              "lang": "en",
              "type": "text"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2018-04-11T09:57:01.000Z",
        "orgId": "8254265b-2729-46b6-b9e3-3dfca2d5bfca",
        "shortName": "mitre"
      },
      "references": [
        {
          "name": "RHSA-2017:3463",
          "tags": [
            "vendor-advisory",
            "x_refsource_REDHAT"
          ],
          "url": "https://access.redhat.com/errata/RHSA-2017:3463"
        },
        {
          "name": "RHSA-2018:0878",
          "tags": [
            "vendor-advisory",
            "x_refsource_REDHAT"
          ],
          "url": "https://access.redhat.com/errata/RHSA-2018:0878"
        },
        {
          "name": "101197",
          "tags": [
            "vdb-entry",
            "x_refsource_BID"
          ],
          "url": "http://www.securityfocus.com/bid/101197"
        },
        {
          "tags": [
            "x_refsource_CONFIRM"
          ],
          "url": "https://golang.org/cl/68210"
        },
        {
          "tags": [
            "x_refsource_CONFIRM"
          ],
          "url": "https://golang.org/cl/68023"
        },
        {
          "tags": [
            "x_refsource_CONFIRM"
          ],
          "url": "https://github.com/golang/go/issues/22134"
        },
        {
          "name": "GLSA-201710-23",
          "tags": [
            "vendor-advisory",
            "x_refsource_GENTOO"
          ],
          "url": "https://security.gentoo.org/glsa/201710-23"
        },
        {
          "tags": [
            "x_refsource_CONFIRM"
          ],
          "url": "https://groups.google.com/d/msg/golang-dev/RinSE3EiJBI/kYL7zb07AgAJ"
        }
      ],
      "x_legacyV4Record": {
        "CVE_data_meta": {
          "ASSIGNER": "cve@mitre.org",
          "ID": "CVE-2017-15042",
          "STATE": "PUBLIC"
        },
        "affects": {
          "vendor": {
            "vendor_data": [
              {
                "product": {
                  "product_data": [
                    {
                      "product_name": "n/a",
                      "version": {
                        "version_data": [
                          {
                            "version_value": "n/a"
                          }
                        ]
                      }
                    }
                  ]
                },
                "vendor_name": "n/a"
              }
            ]
          }
        },
        "data_format": "MITRE",
        "data_type": "CVE",
        "data_version": "4.0",
        "description": {
          "description_data": [
            {
              "lang": "eng",
              "value": "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\u0027t advertise STARTTLS and does advertise that PLAIN auth is OK, the smtp.PlainAuth implementation sends the username and password."
            }
          ]
        },
        "problemtype": {
          "problemtype_data": [
            {
              "description": [
                {
                  "lang": "eng",
                  "value": "n/a"
                }
              ]
            }
          ]
        },
        "references": {
          "reference_data": [
            {
              "name": "RHSA-2017:3463",
              "refsource": "REDHAT",
              "url": "https://access.redhat.com/errata/RHSA-2017:3463"
            },
            {
              "name": "RHSA-2018:0878",
              "refsource": "REDHAT",
              "url": "https://access.redhat.com/errata/RHSA-2018:0878"
            },
            {
              "name": "101197",
              "refsource": "BID",
              "url": "http://www.securityfocus.com/bid/101197"
            },
            {
              "name": "https://golang.org/cl/68210",
              "refsource": "CONFIRM",
              "url": "https://golang.org/cl/68210"
            },
            {
              "name": "https://golang.org/cl/68023",
              "refsource": "CONFIRM",
              "url": "https://golang.org/cl/68023"
            },
            {
              "name": "https://github.com/golang/go/issues/22134",
              "refsource": "CONFIRM",
              "url": "https://github.com/golang/go/issues/22134"
            },
            {
              "name": "GLSA-201710-23",
              "refsource": "GENTOO",
              "url": "https://security.gentoo.org/glsa/201710-23"
            },
            {
              "name": "https://groups.google.com/d/msg/golang-dev/RinSE3EiJBI/kYL7zb07AgAJ",
              "refsource": "CONFIRM",
              "url": "https://groups.google.com/d/msg/golang-dev/RinSE3EiJBI/kYL7zb07AgAJ"
            }
          ]
        }
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "8254265b-2729-46b6-b9e3-3dfca2d5bfca",
    "assignerShortName": "mitre",
    "cveId": "CVE-2017-15042",
    "datePublished": "2017-10-05T21:00:00.000Z",
    "dateReserved": "2017-10-05T00:00:00.000Z",
    "dateUpdated": "2024-08-05T19:42:22.302Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.1"
}

Sightings

Author	Source	Type	Date	Other

Nomenclature

Seen: The vulnerability was mentioned, discussed, or observed by the user.
Confirmed: The vulnerability has been validated from an analyst's perspective.
Published Proof of Concept: A public proof of concept is available for this vulnerability.
Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
Not confirmed: The user expressed doubt about the validity of the vulnerability.
Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.

Detection rules are retrieved from Rulezet.

The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base model, served locally by ML-Gateway. They have not been verified by an analyst and are provided for guidance only.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.

Related by attack behaviour

Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.