Lucene search
+L

8 matches found

Github Security Blog
Github Security Blog
•added 2026/09/17 5:04 p.m.•14 views

RabbitMQ amqp091-go: Plaintext Credential Exposure via Exported PLAIN Authentication Struct Fields

Summary An information disclosure vulnerability exists in the AMQP client implementation's authentication handling configuration. Following a successful connection handshake, the Connection.Config.SASL field stores the Authentication implementation state used to establish the session. For standar...

7CVSS6.2AI score0.00128EPSS
SaveExploits0References6Affected Software1
OSV
OSV
•added 2026/09/16 3:17 p.m.•7 views

AZL-103278 CVE-2026-77407 affecting package telegraf 1.31.0-33

RabbitMQ amqp091-go is a Go AMQP 0.9.1 client. Prior to 1.13.0, PlainAuth values defined in auth.go retain passwords as exported plaintext fields in Connection.Config.SASL after a successful PLAIN authentication handshake. The Connection.openComplete method in connection.go does not clear those...

7CVSS5.9AI score0.00128EPSS
SaveExploits0References1
CVE
CVE
•added 2026/09/16 2:34 p.m.•15 views

CVE-2026-77407

RabbitMQ amqp091-go , a Go AMQP 0.9.1 client, is vulnerable to plaintext credential exposure prior to version 1.13.0. After a successful PLAIN authentication handshake, PlainAuth values in auth.go retain the password as an exported field in Connection.Config.SASL. The Connection.openComplete meth...

7CVSS5.8AI score0.00128EPSS
SaveExploits0References4
OSV
OSV
•added 2026/09/16 2:34 p.m.•6 views

CVE-2026-77407 RabbitMQ amqp091-go: Plaintext Credential Exposure via Exported PLAIN Authentication Struct Fields

RabbitMQ amqp091-go is a Go AMQP 0.9.1 client. Prior to 1.13.0, PlainAuth values defined in auth.go retain passwords as exported plaintext fields in Connection.Config.SASL after a successful PLAIN authentication handshake. The Connection.openComplete method in connection.go does not clear those...

7CVSS5.9AI score
SaveExploits0References6
SUSE CVE
SUSE CVE
•added 2023/02/15 4:38 a.m.•9 views

SUSE CVE-2017-15042

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...

5.9CVSS6.8AI score0.01105EPSS
SaveExploits0References3
RedhatCVE
RedhatCVE
•added 2017/10/06 12:19 a.m.•33 views

CVE-2017-15042

It was found that smtp.PlainAuth authentication scheme in Go did not verify the TLS requirement properly. A remote man-in-the-middle attacker could potentially use this flaw to sniff SMTP credentials sent by a Go application...

5.9CVSS2.8AI score0.01105EPSS
SaveExploits0References1
OSV
OSV
•added 2017/10/05 9:29 p.m.•11 views

UBUNTU-CVE-2017-15042

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...

5.9CVSS6.5AI score0.01105EPSS
SaveExploits0References6
OSV
OSV
•added 2017/10/05 9:29 p.m.•13 views

AZL-79072 CVE-2017-15042 affecting package golang 1.25.7-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...

5.9CVSS6.5AI score0.01105EPSS
SaveExploits0References1
Rows per page
Query Builder