# CVE-2015-5695: Designate mDNS DoS through incorrect handling of large RecordSets

> Remote attackers can cause a denial of service via infinite loop in OpenStack Designate by exploiting missing quota enforcement during zone transfers.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 31 Aug 2017
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2015-5695, GHSA-m6h2-634h-jcpj, PYSEC-2017-114

## What is CVE-2015-5695?

CVE-2015-5695 is a medium-severity denial of service vulnerability in n/a, published on 31 Aug 2017. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Designate 2015.1.0 through 1.0.0.0b1 as packaged in OpenStack Kilo does not enforce RecordSets per domain, and Records per RecordSet quotas when processing an internal zone file transfer, which might allow remote attackers to cause a denial of service (infinite loop) via a crafted resource record set.

Weakness: CWE-400 (Uncontrolled Resource Consumption)

## Which versions are affected by CVE-2015-5695?

3 open source packages ship an affected version, including designate. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `designate` | PyPI | All versions | None |
| `designate` | PyPI | All versions | None |
| `designate` | PyPI | All versions | None |

Products: Openstack Designate.

## How do I fix CVE-2015-5695?

Upgrade to a fixed version.

## Is CVE-2015-5695 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-5695 and fix it if it is affected.

What it is: CVE-2015-5695 is a medium-severity denial of service vulnerability in n/a, published on 31 Aug 2017. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2015-5695 in the wild and no public exploit code.

Affected packages and fixed versions:
- designate (PyPI): affected all versions; no fix listed
- designate (PyPI): affected all versions; no fix listed
- designate (PyPI): affected all versions; no fix listed

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-2015-5695/ (Markdown: https://insights.sbomify.com/CVE-2015-5695/index.md)
```

## Sources

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

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