Skip to main content
No exploitation reportedFix available

CVE-2018-1000858

No exploitation reported by the sources we read.

  • Published2018-12-20
  • WeaknessCWE-352

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

GnuPG version 2.1.12 - 2.2.11 contains a Cross ite Request Forgery (CSRF) vulnerability in dirmngr that can result in Attacker controlled CSRF, Information Disclosure, DoS. This attack appear to be exploitable via Victim must perform a WKD request, e.g. enter an email address in the composer window of Thunderbird/Enigmail. This vulnerability appears to have been fixed in after commit 4a4bb874f63741026bd26264c43bb32b1099f060.

Timeline

dates in UTC
  1. 2018-12-2017:29CVE publishedNVD

Versions per branch

NVD
Canonical ubuntu linux
BranchAffectedFixed in
18.4= 18.04no fix published
18.10= 18.10no fix published
Gnupg
BranchAffectedFixed in
2.x≥ 2.1.12, ≤ 2.2.11no fix published

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • gnupg2Ubuntu:18.04:LTSall versions · fixed in 2.2.4-1ubuntu1.2
  • gnupg2Rocky Linux:8all versions · fixed in 0:2.2.20-2.el8
  • gnupg2Red Hat:enterprise_linux:8::baseosall versions · fixed in 0:2.2.20-2.el8and 4 other packages
  • gnupg2Mageia:6all versions · fixed in 2.1.21-3.2.mga6
  • gnupg2Debian:14all versions · fixed in 2.2.12-1
  • gnupg2Debian:13all versions · fixed in 2.2.12-1
  • gnupg2Debian:12all versions · fixed in 2.2.12-1
  • gnupg2AlmaLinux:8all versions · fixed in 2.2.20-2.el8and 1 other package

2 more package ranges on OSV.dev

Vendor advisories

  • CVE-2018-1000858 Red Hat Product Security21 products fixed

    gnupg2: Cross site request forgery in dirmngr resulting in an information disclosure or denial of service

  • RHSA-2020:4490 Red Hat Product Security21 products fixed

    Red Hat Security Advisory: gnupg2 security, bug fix, and enhancement update

Full record on NVD

Fix

  1. Vendor fix Red Hat Product Security RHSA-2020:4490 · 21 productsFor details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Published
2018-12-20
Last Modified
2026-06-17
NVD status
Modified
GitHub Advisory
GHSA-44cw-f8qw-mf2h

Frequently asked questions

What is CVE-2018-1000858?

GnuPG version 2.1.12 - 2.2.11 contains a Cross ite Request Forgery (CSRF) vulnerability in dirmngr that can result in Attacker controlled CSRF, Information Disclosure, DoS. This attack appear to be exploitable via Victim must perform a WKD request, e.g. enter an email address in the composer window of Thunderbird/Enigmail. This vulnerability appears to have been fixed in after commit 4a4bb874f63741026bd26264c43bb32b1099f060.

Is CVE-2018-1000858 actively exploited?

Active exploitation of CVE-2018-1000858 has not been confirmed. Its EPSS score was 1.0% on 2026-11-09, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2018-1000858?

CVE-2018-1000858 has a CVSS v3 base score of 8.8 (HIGH severity), with vector string CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H.

Running gnupg2? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month

Sources for this record