Interaction between the sks-keyserver code through 1.2.0 of the SKS keyserver network, and GnuPG through 2.2.16, makes it risky to have a Gn
Interaction between the sks-keyserver code through 1.2.0 of the SKS keyserver network, and GnuPG through 2.2.16, makes it risky to have a GnuPG keyserver configuration line referring to a host on the SKS keyserver network. Retrieving data from this network may cause a persistent denial of service, because of a Certificate Spamming Attack.
- Published
- Jun 29, 2019
- Updated
- Jun 16, 2026
- EPSS
- 2.7% · 85th percentile
- CWE
- CWE-295
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 2.7%
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| gnupg | gnupg | cpe:2.3:a:gnupg:gnupg |
| sks keyserver project | sks keyserver | cpe:2.3:a:sks_keyserver_project:sks_keyserver |
| fedoraproject | fedora | cpe:2.3:o:fedoraproject:fedora |
| opensuse | leap | cpe:2.3:o:opensuse:leap |
| f5 | traffix signaling delivery controller | cpe:2.3:a:f5:traffix_signaling_delivery_controller |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- f5 traffix signaling delivery controller5.0.0 and later · up to 5.1.0 inclusive
- fedoraproject fedora29
- fedoraproject fedora30
- gnupg gnupgup to 2.2.16 inclusive
- opensuse leap15.0
- opensuse leap15.1
- sks keyserver project sks keyserverup to 1.2.0 inclusive
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:8 | gnupg2 | before 2.2.20-2.el8 | 2.2.20-2.el8 |
| AlmaLinux:8 | gnupg2-smime | before 2.2.20-2.el8 | 2.2.20-2.el8 |
| openSUSE:Leap 15.0 | gpg2 | before 2.2.5-lp151.6.3.1 | 2.2.5-lp151.6.3.1 |
| Red Hat:enterprise_linux:8::baseos | gnupg2 | before 0:2.2.20-2.el8 | 0:2.2.20-2.el8 |
| Red Hat:enterprise_linux:8::baseos | gnupg2-debuginfo | before 0:2.2.20-2.el8 | 0:2.2.20-2.el8 |
| Red Hat:enterprise_linux:8::baseos | gnupg2-debugsource | before 0:2.2.20-2.el8 | 0:2.2.20-2.el8 |
| Red Hat:enterprise_linux:8::baseos | gnupg2-smime | before 0:2.2.20-2.el8 | 0:2.2.20-2.el8 |
| Red Hat:enterprise_linux:8::baseos | gnupg2-smime-debuginfo | before 0:2.2.20-2.el8 | 0:2.2.20-2.el8 |
| Rocky Linux:8 | gnupg2 | before 0:2.2.20-2.el8 | 0:2.2.20-2.el8 |
| SUSE:Linux Enterprise Desktop 12 SP4 | gpg2 | before 2.0.24-9.8.1 | 2.0.24-9.8.1 |
| SUSE:Linux Enterprise Module for Basesystem 15 | gpg2 | before 2.2.5-4.11.1 | 2.2.5-4.11.1 |
Same product
gnupg: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-24881In GnuPG before 2.5.17, a crafted CMS (S/MIME) EnvelopedData message carrying an oversized wrapped session key can cause a stack-based buffe40Plan
- CVE-2008-1530GnuPG (gpg) 1.4.8 and 2.0.8 allows remote attackers to cause a denial of service (crash) and possibly execute arbitrary code via crafted dup38Monitor
- CVE-2018-1000858GnuPG version 2.1.12 - 2.2.11 contains a Cross ite Request Forgery (CSRF) vulnerability in dirmngr that can result in Attacker controlled CS35Monitor
- CVE-2010-2547Use-after-free vulnerability in kbx/keybox-blob.c in GPGSM in GnuPG 2.x through 2.0.16 allows remote attackers to cause a denial of service 34Monitor
- CVE-2018-12020mainproc.c in GnuPG before 2.2.8 mishandles the original filename during decryption and verification actions, which allows remote attackers 33Monitor
- CVE-2026-24882In GnuPG before 2.5.17, a stack-based buffer overflow exists in tpm2daemon during handling of the PKDECRYPT command for TPM-backed RSA and E31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| almalinux:gnupg2 | 2.2.20-2.el8 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:gnupg2-smime | 2.2.20-2.el8 · AlmaLinux:8 | Package registry (OSV) |
| opensuse:gpg2 | 2.2.5-lp151.6.3.1 · openSUSE:Leap 15.0 | Package registry (OSV) |
| red hat:gnupg2 | 0:2.2.20-2.el8 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:gnupg2-debuginfo | 0:2.2.20-2.el8 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:gnupg2-debugsource | 0:2.2.20-2.el8 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:gnupg2-smime | 0:2.2.20-2.el8 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:gnupg2-smime-debuginfo | 0:2.2.20-2.el8 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| rocky linux:gnupg2 | 0:2.2.20-2.el8 · Rocky Linux:8 | Package registry (OSV) |
| suse:gpg2 | 2.2.5-4.11.1 · SUSE:Linux Enterprise Module for Basesystem 15 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-295 · Improper Certificate ValidationCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Root cause
A certificate validation error is silently swallowed instead of terminating the connection. Often, code added for a test environment makes its way into production.
The bug in code
The whole CWE-295 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
override fun checkServerTrusted(chain: Array<X509Certificate>, type: String) { // Left empty for the test environment}Fixed
val client = OkHttpClient.Builder() .certificatePinner( CertificatePinner.Builder() .add("api.sirius.example", "sha256/…") .build() ).build()Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
- lists.opensuse.org/opensuse-security-announce/2019-08/msg00039.html
- lists.apache.org/thread.html/r58af02e294bd07f487e2c64ffc0a29b837db5600e33b6e698b9d696b%40%3Cissues.bookkeeper.apache.org%3E
- lists.apache.org/thread.html/rf4c02775860db415b4955778a131c2795223f61cb8c6a450893651e4%40%3Cissues.bookkeeper.apache.org%3E
- lists.apache.org/thread.html/rf9fa47ab66495c78bb4120b0754dd9531ca2ff0430f6685ac9b07772%40%3Cdev.mina.apache.org%3E
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/AUK2YRO6QIH64WP2LRA5D4LACTXQPPU4/
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/CP4ON34YEXEZDZOXXWV43KVGGO6WZLJ5/
- lists.gnupg.org/pipermail/gnupg-announce/2019q3/000439.html
- support.f5.com/csp/article/K08654551
- support.f5.com/csp/article/K08654551?utm_source=f5support&%3Butm_medium=RSS
- twitter.com/lambdafu/status/1147162583969009664
Vendor advisories and official records. Exploit/PoC links are deliberately left out.