CVE-2019-11841

See a problem?
Source
https://nvd.nist.gov/vuln/detail/CVE-2019-11841
Import Source
https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2019-11841.json
JSON Data
https://api.osv.dev/v1/vulns/CVE-2019-11841
Aliases
Related
Published
2019-05-22T17:29:00Z
Modified
2024-09-18T01:00:22Z
Severity
  • 5.9 (Medium) CVSS_V3 - CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N CVSS Calculator
Summary
[none]
Details

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

Affected packages

Debian:11 / golang-go.crypto

Package

Name
golang-go.crypto
Purl
pkg:deb/debian/golang-go.crypto?arch=source

Affected ranges

Type
ECOSYSTEM
Events
Introduced
0Unknown introduced version / All previous versions are affected
Fixed
1:0.0~git20200221.2aa609c-1

Ecosystem specific

{
    "urgency": "not yet assigned"
}

Debian:12 / golang-go.crypto

Package

Name
golang-go.crypto
Purl
pkg:deb/debian/golang-go.crypto?arch=source

Affected ranges

Type
ECOSYSTEM
Events
Introduced
0Unknown introduced version / All previous versions are affected
Fixed
1:0.0~git20200221.2aa609c-1

Ecosystem specific

{
    "urgency": "not yet assigned"
}

Debian:13 / golang-go.crypto

Package

Name
golang-go.crypto
Purl
pkg:deb/debian/golang-go.crypto?arch=source

Affected ranges

Type
ECOSYSTEM
Events
Introduced
0Unknown introduced version / All previous versions are affected
Fixed
1:0.0~git20200221.2aa609c-1

Ecosystem specific

{
    "urgency": "not yet assigned"
}