Cryptographic Issues Affecting golang-go.crypto package, versions <1:0.0~git20200221.2aa609c-1


Severity

Recommended
0.0
medium
0
10

Snyk's Security Team recommends NVD's CVSS assessment. Learn more

Threat Intelligence

EPSS
0.87% (84th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications

Snyk Learn

Learn about Cryptographic Issues vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-DEBIANUNSTABLE-GOLANGGOCRYPTO-452551
  • published15 May 2019
  • disclosed22 May 2019

Introduced: 15 May 2019

CVE-2019-11841  (opens in a new tab)
CWE-310  (opens in a new tab)

How to fix?

Upgrade Debian:unstable golang-go.crypto to version 1:0.0~git20200221.2aa609c-1 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream golang-go.crypto package and not the golang-go.crypto package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

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.

CVSS Scores

version 3.1