# CVE-2019-13050: Denial of service in n/a

> Retrieving data from SKS keyserver network causes persistent denial of service via certificate spamming, requiring users to avoid SKS hosts in GnuPG config.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 29 Jun 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-ch5h-mpfr-fhxh, SUSE-SU-2019:2006-1, SUSE-SU-2019:2480-1, UBUNTU-CVE-2019-13050, USN-5431-1, openSUSE-SU-2019:1917-1

## What is CVE-2019-13050?

CVE-2019-13050 is a high-severity denial of service vulnerability in Fedoraproject Fedora, published on 29 Jun 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-295 (Improper Certificate Validation)

## Which versions are affected by CVE-2019-13050?

It affects 5 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `gpg2` | SUSE:Linux Enterprise Desktop 12 SP4 | All versions | 2.0.24-9.8.1 |
| `gpg2` | SUSE:Linux Enterprise Module for Basesystem 15 | All versions | 2.2.5-4.11.1 |
| `gpg2` | SUSE:Linux Enterprise Module for Basesystem 15 SP1 | All versions | 2.2.5-4.11.1 |
| `gpg2` | SUSE:Linux Enterprise Server 12 SP4 | All versions | 2.0.24-9.8.1 |
| `gpg2` | SUSE:Linux Enterprise Server for SAP Applications 12 SP4 | All versions | 2.0.24-9.8.1 |
| `gpg2` | openSUSE:Leap 15.0 | All versions | 2.2.5-lp151.6.3.1 |
| `gpg2` | openSUSE:Leap 15.1 | All versions | 2.2.5-lp151.6.3.1 |

Products: F5 Traffix Signaling Delivery Controller, Fedoraproject Fedora, Gnupg Gnupg, Opensuse Leap, Sks Keyserver Project Sks Keyserver.

## How do I fix CVE-2019-13050?

Change a configuration setting.

## Is CVE-2019-13050 being exploited?

There is no known exploitation of CVE-2019-13050 in the wild and no public exploit code.

## Other vulnerabilities in Fedoraproject Fedora

- [CVE-2018-20657](https://insights.sbomify.com/CVE-2018-20657/): Denial of service in n/a (high 7.5)
- [CVE-2015-5738](https://insights.sbomify.com/CVE-2015-5738/): Information disclosure in n/a (high 7.5)
- [CVE-2018-20002](https://insights.sbomify.com/CVE-2018-20002/): Denial of service in n/a (medium 5.5)
- [CVE-2022-27662](https://insights.sbomify.com/CVE-2022-27662/): Code injection in Traffix SDC (medium 4.8)
- [CVE-2022-27880](https://insights.sbomify.com/CVE-2022-27880/): Cross-site scripting in Traffix SDC (medium 4.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-13050 and fix it if it is affected.

What it is: CVE-2019-13050 is a high-severity denial of service vulnerability in Fedoraproject Fedora, published on 29 Jun 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-13050 in the wild and no public exploit code.

Affected product: Fedoraproject Fedora. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2019-13050/ (Markdown: https://insights.sbomify.com/CVE-2019-13050/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2019-13050
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-13050
- OSV: https://osv.dev/vulnerability/CVE-2019-13050

---
From sbomify Insights: https://insights.sbomify.com/CVE-2019-13050/
Summaries are generated and may contain mistakes; the official description above is the record.