# CVE-2017-15130: Denial of service in dovecot

> An attacker can cause excessive memory usage and service restarts in Dovecot by generating random TLS SNI server names.

- **Severity:** Medium 5.9 (`CVSS:3.0/AV:N/AC:H/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:** 2 Mar 2018
- **Updated:** 16 Sep 2024
- **Also known as:** ALPINE-CVE-2017-15130, DEBIAN-CVE-2017-15130, GHSA-36px-qc55-gxh7, SUSE-SU-2018:2632-1, SUSE-SU-2018:2632-2, UBUNTU-CVE-2017-15130

## What is CVE-2017-15130?

CVE-2017-15130 is a medium-severity denial of service vulnerability in Canonical Ubuntu Linux, published on 2 Mar 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A denial of service flaw was found in dovecot before 2.2.34. An attacker able to generate random SNI server names could exploit TLS SNI configuration lookups, leading to excessive memory usage and the process to restart.

Weakness: CWE-400 (Uncontrolled Resource Consumption)

## Which versions are affected by CVE-2017-15130?

It affects 3 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `dovecot22` | SUSE:Enterprise Storage 4 | All versions | 2.2.31-19.11.1 |
| `dovecot22` | SUSE:Linux Enterprise Server 12 SP1-LTSS | All versions | 2.2.31-19.11.1 |
| `dovecot22` | SUSE:Linux Enterprise Server 12 SP2-BCL | All versions | 2.2.31-19.11.1 |
| `dovecot22` | SUSE:Linux Enterprise Server 12 SP2-LTSS | All versions | 2.2.31-19.11.1 |
| `dovecot22` | SUSE:Linux Enterprise Server 12 SP3 | All versions | 2.2.31-19.11.1 |
| `dovecot22` | SUSE:Linux Enterprise Server 12-LTSS | All versions | 2.2.31-19.11.1 |
| `dovecot22` | SUSE:Linux Enterprise Server for SAP Applications 12 SP1 | All versions | 2.2.31-19.11.1 |
| `dovecot22` | SUSE:Linux Enterprise Server for SAP Applications 12 SP2 | All versions | 2.2.31-19.11.1 |
| `dovecot22` | SUSE:Linux Enterprise Server for SAP Applications 12 SP3 | All versions | 2.2.31-19.11.1 |
| `dovecot22` | SUSE:Linux Enterprise Software Development Kit 12 SP3 | All versions | 2.2.31-19.11.1 |
| `dovecot22` | SUSE:OpenStack Cloud 7 | All versions | 2.2.31-19.11.1 |

Products: Canonical Ubuntu Linux, Debian Debian Linux, Dovecot Dovecot.

## How do I fix CVE-2017-15130?

Upgrade to a fixed version.

## Is CVE-2017-15130 being exploited?

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

## Other vulnerabilities in Canonical Ubuntu Linux

- [CVE-2020-11651](https://insights.sbomify.com/CVE-2020-11651/): SaltStack Salt Authentication Bypass (critical 9.8, exploited in the wild)
- [CVE-2020-7247](https://insights.sbomify.com/CVE-2020-7247/): OpenSMTPD Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2019-16928](https://insights.sbomify.com/CVE-2019-16928/): Exim Out-of-bounds Write (critical 9.8, exploited in the wild)
- [CVE-2018-6789](https://insights.sbomify.com/CVE-2018-6789/): Exim Buffer Overflow (critical 9.8, exploited in the wild)
- [CVE-2015-2590](https://insights.sbomify.com/CVE-2015-2590/): Oracle Java SE and Java SE Embedded Remote Code Execution (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-15130 and fix it if it is affected.

What it is: CVE-2017-15130 is a medium-severity denial of service vulnerability in Canonical Ubuntu Linux, published on 2 Mar 2018. 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-2017-15130 in the wild and no public exploit code.

Affected product: Canonical Ubuntu Linux. 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-2017-15130/ (Markdown: https://insights.sbomify.com/CVE-2017-15130/index.md)
```

## Sources

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

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