Approved changes feed: RSS · Atom
cpe:2.3:a:golang:go:1.9:*:*:*:*:*:*:*
part: a version: 1.9 update: *
| Vendor | Golang (670356c5-bd1b-5c66-9eee-f755f5cec4c7) |
|---|---|
| Product | Go (96a6ef33-04c7-5363-bbc8-7d2a06bf0b4b) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2018-6574 |
vulnerable | 2026-06-03 14:39:00.525009 |
Details available
Go before 1.8.7, Go 1.9.x before 1.9.4, and Go 1.10 pre-releases before Go 1.10rc2 allow "go get" remote command execution during source code build, by leveraging the gcc or clang plugin feature, because -fplugin= and -plugin= arguments were not blocked.
Published: 2018-02-07T21:00:00.000Z
Updated: 2024-08-05T06:10:10.226Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2017-15042 |
vulnerable | 2026-06-03 14:36:45.186292 |
Details available
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.
Published: 2017-10-05T21:00:00.000Z
Updated: 2024-08-05T19:42:22.302Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.