golang.org/x/crypto
Affected
- introduced
0, fixed0.0.0-20190424203555-c05e17bb3b2d(semver)
Fixed versions
0.0.0-20190424203555-c05e17bb3b2d
Fix
- Fixed version
0.0.0-20190424203555-c05e17bb3b2dgo get golang.org/x/[email protected]
Advisory
Also known as: CVE-2019-11841, GO-2023-1992
Golang/x/crypto message forgery vulnerability
A message-forgery issue was discovered in crypto/openpgp/clearsign/clearsign.go in supplementary Go cryptography libraries 2019-03-25. According to the OpenPGP Message Format specification in RFC 4880 chapter 7, a cleartext signed message can contain one or more optional "Hash" Armor Headers. The "Hash" Armor Header specifies the message digest algorithm(s) used for the signature. However, the Go clearsign package ignores the value of this header, which allows an attacker to spoof it. Consequently, an attacker can lead a victim to believe the signature was generated using a different message digest algorithm than what was actually used. Moreover, since the library skips Armor Header parsing in general, an attacker can not only embed arbitrary Armor Headers, but also prepend arbitrary text to cleartext messages without invalidating the signatures.
Medium Basis: The source's own band: MODERATE
0, fixed 0.0.0-20190424203555-c05e17bb3b2d (semver)0.0.0-20190424203555-c05e17bb3b2d
0.0.0-20190424203555-c05e17bb3b2dgo get golang.org/x/[email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0