An open API service providing security vulnerability metadata for many open source software ecosystems.

GSA_kwCzR0hTQS14M2pyLXBmNmctYzQ4Zs4AAgxZ

Moderate EPSS: 0.0039% (0.59147 Percentile) EPSS:

Golang/x/crypto message forgery vulnerability

Affected Packages Affected Versions Fixed Versions
go:golang.org/x/crypto < 0.0.0-20190424203555-c05e17bb3b2d 0.0.0-20190424203555-c05e17bb3b2d
125,672 Dependent packages
269,003 Dependent repositories

Affected Version Ranges

All affected versions

All unaffected versions

0.1.0, 0.2.0, 0.3.0, 0.4.0, 0.5.0, 0.6.0, 0.7.0, 0.8.0, 0.9.0, 0.10.0, 0.11.0, 0.12.0, 0.13.0, 0.14.0, 0.15.0, 0.16.0, 0.17.0, 0.18.0, 0.19.0, 0.20.0, 0.21.0, 0.22.0, 0.23.0, 0.24.0, 0.25.0, 0.26.0, 0.27.0, 0.28.0, 0.29.0, 0.30.0, 0.31.0, 0.32.0, 0.33.0, 0.34.0, 0.35.0, 0.36.0, 0.37.0, 0.38.0, 0.39.0, 0.40.0

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.

References: