{"api_version":"1","generated_at":"2026-04-23T07:56:24+00:00","cve":"CVE-2019-11841","urls":{"html":"https://cve.report/CVE-2019-11841","api":"https://cve.report/api/cve/CVE-2019-11841.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2019-11841","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2019-11841"},"summary":{"title":"CVE-2019-11841","description":"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.","state":"PUBLIC","assigner":"cve@mitre.org","published_at":"2019-05-22 17:29:00","updated_at":"2023-06-17 00:15:00"},"problem_types":["CWE-347"],"metrics":[],"references":[{"url":"https://lists.debian.org/debian-lts-announce/2019/09/msg00011.html","name":"[debian-lts-announce] 20190913 [SECURITY] [DLA 1920-1] golang-go.crypto security update","refsource":"MLIST","tags":[],"title":"[SECURITY] [DLA 1920-1] golang-go.crypto security update","mime":"text/html","httpstatus":"200","archivestatus":"200"},{"url":"https://lists.debian.org/debian-lts-announce/2020/10/msg00014.html","name":"[debian-lts-announce] 20201007 [SECURITY] [DLA 2402-1] golang-go.crypto security update","refsource":"MLIST","tags":[],"title":"[SECURITY] [DLA 2402-1] golang-go.crypto security update","mime":"text/html","httpstatus":"200","archivestatus":"200"},{"url":"https://go.googlesource.com/crypto/","name":"https://go.googlesource.com/crypto/","refsource":"MISC","tags":["Product","Third Party Advisory"],"title":"crypto - Git at Google","mime":"text/html","httpstatus":"200","archivestatus":"200"},{"url":"https://sec-consult.com/en/blog/advisories/cleartext-message-spoofing-in-go-cryptography-libraries-cve-2019-11841/","name":"https://sec-consult.com/en/blog/advisories/cleartext-message-spoofing-in-go-cryptography-libraries-cve-2019-11841/","refsource":"MISC","tags":["Exploit","Third Party Advisory"],"title":"Cleartext message spoofing in Go Cryptography Libraries (CVE-2019-11841) – SEC Consult","mime":"text/html","httpstatus":"404","archivestatus":"200"},{"url":"https://lists.debian.org/debian-lts-announce/2023/06/msg00017.html","name":"[debian-lts-announce] 20230616 [SECURITY] [DLA 3455-1] golang-go.crypto security update","refsource":"MLIST","tags":[],"title":"[SECURITY] [DLA 3455-1] golang-go.crypto security update","mime":"text/html","httpstatus":"200","archivestatus":"404"},{"url":"https://sec-consult.com/","name":"https://sec-consult.com/","refsource":"MISC","tags":["Third Party Advisory"],"title":"HP","mime":"text/html","httpstatus":"200","archivestatus":"200"},{"url":"http://packetstormsecurity.com/files/152840/Go-Cryptography-Libraries-Cleartext-Message-Spoofing.html","name":"http://packetstormsecurity.com/files/152840/Go-Cryptography-Libraries-Cleartext-Message-Spoofing.html","refsource":"MISC","tags":["Exploit","Third Party Advisory","VDB Entry"],"title":"Go Cryptography Libraries Cleartext Message Spoofing ≈ Packet Storm","mime":"text/html","httpstatus":"200","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2019-11841","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2019-11841","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[{"cve_year":"2019","cve_id":"11841","vulnerable":"1","versionEndIncluding":"","cpe1":"cpe","cpe2":"2.3","cpe3":"o","cpe4":"debian","cpe5":"debian_linux","cpe6":"8.0","cpe7":"*","cpe8":"*","cpe9":"*","cpe10":"*","cpe11":"*","cpe12":"*","cpe13":"*"},{"cve_year":"2019","cve_id":"11841","vulnerable":"1","versionEndIncluding":"","cpe1":"cpe","cpe2":"2.3","cpe3":"o","cpe4":"debian","cpe5":"debian_linux","cpe6":"9.0","cpe7":"*","cpe8":"*","cpe9":"*","cpe10":"*","cpe11":"*","cpe12":"*","cpe13":"*"},{"cve_year":"2019","cve_id":"11841","vulnerable":"1","versionEndIncluding":"","cpe1":"cpe","cpe2":"2.3","cpe3":"a","cpe4":"golang","cpe5":"crypto","cpe6":"2019-03-25","cpe7":"*","cpe8":"*","cpe9":"*","cpe10":"*","cpe11":"*","cpe12":"*","cpe13":"*"},{"cve_year":"2019","cve_id":"11841","vulnerable":"1","versionEndIncluding":"1","cpe1":"cpe","cpe2":"2.3","cpe3":"a","cpe4":"golang","cpe5":"crypto","cpe6":"2019-03-25","cpe7":"*","cpe8":"*","cpe9":"*","cpe10":"*","cpe11":"*","cpe12":"*","cpe13":"*"}],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[{"cve":"CVE-2019-11841","qid":"181874","title":"Debian Security Update for golang-go.crypto (DLA 3455-1)"}]},"source_records":{"cve_program":{"CVE_data_meta":{"ASSIGNER":"cve@mitre.org","ID":"CVE-2019-11841","STATE":"PUBLIC"},"affects":{"vendor":{"vendor_data":[{"product":{"product_data":[{"product_name":"n/a","version":{"version_data":[{"version_value":"n/a"}]}}]},"vendor_name":"n/a"}]}},"data_format":"MITRE","data_type":"CVE","data_version":"4.0","description":{"description_data":[{"lang":"eng","value":"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."}]},"problemtype":{"problemtype_data":[{"description":[{"lang":"eng","value":"n/a"}]}]},"references":{"reference_data":[{"url":"https://sec-consult.com/","refsource":"MISC","name":"https://sec-consult.com/"},{"url":"https://go.googlesource.com/crypto/","refsource":"MISC","name":"https://go.googlesource.com/crypto/"},{"refsource":"MISC","name":"http://packetstormsecurity.com/files/152840/Go-Cryptography-Libraries-Cleartext-Message-Spoofing.html","url":"http://packetstormsecurity.com/files/152840/Go-Cryptography-Libraries-Cleartext-Message-Spoofing.html"},{"refsource":"MISC","name":"https://sec-consult.com/en/blog/advisories/cleartext-message-spoofing-in-go-cryptography-libraries-cve-2019-11841/","url":"https://sec-consult.com/en/blog/advisories/cleartext-message-spoofing-in-go-cryptography-libraries-cve-2019-11841/"},{"refsource":"MLIST","name":"[debian-lts-announce] 20190913 [SECURITY] [DLA 1920-1] golang-go.crypto security update","url":"https://lists.debian.org/debian-lts-announce/2019/09/msg00011.html"},{"refsource":"MLIST","name":"[debian-lts-announce] 20201007 [SECURITY] [DLA 2402-1] golang-go.crypto security update","url":"https://lists.debian.org/debian-lts-announce/2020/10/msg00014.html"},{"refsource":"MLIST","name":"[debian-lts-announce] 20230616 [SECURITY] [DLA 3455-1] golang-go.crypto security update","url":"https://lists.debian.org/debian-lts-announce/2023/06/msg00017.html"}]}},"nvd":{"publishedDate":"2019-05-22 17:29:00","lastModifiedDate":"2023-06-17 00:15:00","problem_types":["CWE-347"],"metrics":{"baseMetricV3":{"cvssV3":{"version":"3.1","vectorString":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N","attackVector":"NETWORK","attackComplexity":"HIGH","privilegesRequired":"NONE","userInteraction":"NONE","scope":"UNCHANGED","confidentialityImpact":"NONE","integrityImpact":"HIGH","availabilityImpact":"NONE","baseScore":5.9,"baseSeverity":"MEDIUM"},"exploitabilityScore":2.2,"impactScore":3.6},"baseMetricV2":{"cvssV2":{"version":"2.0","vectorString":"AV:N/AC:M/Au:N/C:N/I:P/A:N","accessVector":"NETWORK","accessComplexity":"MEDIUM","authentication":"NONE","confidentialityImpact":"NONE","integrityImpact":"PARTIAL","availabilityImpact":"NONE","baseScore":4.3},"severity":"MEDIUM","exploitabilityScore":8.6,"impactScore":2.9,"acInsufInfo":false,"obtainAllPrivilege":false,"obtainUserPrivilege":false,"obtainOtherPrivilege":false,"userInteractionRequired":false}},"configurations":{"CVE_data_version":"4.0","nodes":[{"operator":"OR","children":[],"cpe_match":[{"vulnerable":true,"cpe23Uri":"cpe:2.3:a:golang:crypto:2019-03-25:*:*:*:*:*:*:*","cpe_name":[]}]},{"operator":"OR","children":[],"cpe_match":[{"vulnerable":true,"cpe23Uri":"cpe:2.3:o:debian:debian_linux:8.0:*:*:*:*:*:*:*","cpe_name":[]},{"vulnerable":true,"cpe23Uri":"cpe:2.3:o:debian:debian_linux:9.0:*:*:*:*:*:*:*","cpe_name":[]}]}]}},"legacy_mitre":{"record":{"CveYear":"2019","CveId":"11841","Ordinal":"150164","Title":"CVE-2019-11841","CVE":"CVE-2019-11841","Year":"2019"},"notes":[{"CveYear":"2019","CveId":"11841","Ordinal":"1","NoteData":"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.","Type":"Description","Title":null},{"CveYear":"2019","CveId":"11841","Ordinal":"2","NoteData":"2019-05-22","Type":"Other","Title":"Published"},{"CveYear":"2019","CveId":"11841","Ordinal":"3","NoteData":"2020-10-07","Type":"Other","Title":"Modified"}]}}}