Google Go up to 1.8.3/1.9.0 SMTP information disclosure

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
6.2$0-$5k0.00

Summaryinfo

A vulnerability was found in Google Go up to 1.8.3/1.9.0. It has been rated as critical. Affected by this issue is some unknown functionality of the component SMTP. The manipulation leads to information disclosure. This vulnerability is handled as CVE-2017-15042. The attack may be launched remotely. There is no exploit available. It is recommended to upgrade the affected component. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Detailsinfo

A vulnerability was found in Google Go up to 1.8.3/1.9.0 (Programming Language Software). It has been declared as critical. Affected by this vulnerability is an unknown code block of the component SMTP. The manipulation with an unknown input leads to a information disclosure vulnerability. The CWE definition for the vulnerability is CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

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.

The bug was discovered 10/05/2017. The weakness was shared 10/05/2017 (GitHub Repository). It is possible to read the advisory at github.com. This vulnerability is known as CVE-2017-15042 since 10/05/2017. The attack can be launched remotely. The exploitation doesn't need any form of authentication. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1592 according to MITRE ATT&CK.

The vulnerability scanner Nessus provides a plugin with the ID 103899 (Fedora 26 : golang (2017-6f1b90dbb7)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Fedora Local Security Checks and running in the context l. The commercial vulnerability scanner Qualys is able to test this issue with plugin 276932 (Fedora Security Update for golang (FEDORA-2017-8f7bca960b)).

Upgrading to version 1.8.4 or 1.9.1 eliminates this vulnerability. A possible mitigation has been published 2 weeks after the disclosure of the vulnerability.

The vulnerability is also documented in the databases at Tenable (103899) and SecurityFocus (BID 101197†). The entry VDB-107538 is related to this item. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

Vendor

Name

Version

License

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 6.6
VulDB Meta Temp Score: 6.2

VulDB Base Score: 7.3
VulDB Temp Score: 6.4
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 5.9
NVD Vector: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
unlockunlockunlockunlockunlockunlock
unlockunlockunlockunlockunlockunlock
unlockunlockunlockunlockunlockunlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍

Exploitinginfo

Class: Information disclosure
CWE: CWE-200 / CWE-284 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍

Local: No
Remote: Yes

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-Dayunlockunlockunlockunlock
Todayunlockunlockunlockunlock

Nessus ID: 103899
Nessus Name: Fedora 26 : golang (2017-6f1b90dbb7)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

OpenVAS ID: 867773
OpenVAS Name: Fedora Update for golang FEDORA-2017-8f7bca960b
OpenVAS File: 🔍
OpenVAS Family: 🔍

Qualys ID: 🔍
Qualys Name: 🔍

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍

Upgrade: Go 1.8.4/1.9.1

Timelineinfo

10/04/2017 🔍
10/05/2017 +1 days 🔍
10/05/2017 +0 days 🔍
10/05/2017 +0 days 🔍
10/05/2017 +0 days 🔍
10/06/2017 +1 days 🔍
10/17/2017 +11 days 🔍
10/18/2017 +1 days 🔍
12/30/2022 +1899 days 🔍

Sourcesinfo

Vendor: google.com

Advisory: FEDORA-2017-6f1b90dbb7
Researcher: Stevie Johnstone
Status: Not defined
Confirmation: 🔍

CVE: CVE-2017-15042 (🔍)
GCVE (CVE): GCVE-0-2017-15042
GCVE (VulDB): GCVE-100-107539
SecurityFocus: 101197

See also: 🔍

Entryinfo

Created: 10/06/2017 10:10 AM
Updated: 12/30/2022 08:28 PM
Changes: 10/06/2017 10:10 AM (76), 03/28/2020 02:12 PM (3), 01/15/2021 06:12 PM (5), 12/30/2022 08:22 PM (3), 12/30/2022 08:28 PM (1)
Complete: 🔍
Cache ID: 18:A5A:40

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you know our Splunk app?

Download it now for free!