# CVE-2018-14663: Other in dnsdist

> Remote attackers can bypass DNS firewall filtering by smuggling trailing data as valid records when specific EDNS features are enabled.

- **Severity:** Medium 5.9 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 Nov 2018
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2018-14663, GHSA-r2j7-9v32-854m, UBUNTU-CVE-2018-14663

## What is CVE-2018-14663?

CVE-2018-14663 is a medium-severity vulnerability in [UNKNOWN] dnsdist, published on 26 Nov 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue has been found in PowerDNS DNSDist before 1.3.3 allowing a remote attacker to craft a DNS query with trailing data such that the addition of a record by dnsdist, for example an OPT record when adding EDNS Client Subnet, might result in the trailing data being smuggled to the backend as a valid record while not seen by dnsdist. This is an issue when dnsdist is deployed as a DNS Firewall and used to filter some records that should not be received by the backend. This issue occurs only when either the 'useClientSubnet' or the experimental 'addXPF' parameters are used when declaring a new backend.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2018-14663?

It affects 1 product.


Products: Powerdns Dnsdist.

## How do I fix CVE-2018-14663?

Upgrade to a fixed version.

## Is CVE-2018-14663 being exploited?

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

## Other vulnerabilities in [UNKNOWN] dnsdist

- [CVE-2017-7557](https://insights.sbomify.com/CVE-2017-7557/): Cross-site request forgery in dnsdist (high 8.8)
- [CVE-2026-33593](https://insights.sbomify.com/CVE-2026-33593/): Denial of service via crafted DNSCrypt query (high 7.5)
- [CVE-2026-33602](https://insights.sbomify.com/CVE-2026-33602/): Off-by-one access when processing crafted UDP responses (medium 6.5)
- [CVE-2026-24029](https://insights.sbomify.com/CVE-2026-24029/): DNS over HTTPS ACL bypass (medium 6.5)
- [CVE-2026-27853](https://insights.sbomify.com/CVE-2026-27853/): Out-of-bounds write when rewriting large DNS packets (medium 5.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-14663 and fix it if it is affected.

What it is: CVE-2018-14663 is a medium-severity vulnerability in [UNKNOWN] dnsdist, published on 26 Nov 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-2018-14663 in the wild and no public exploit code.

Affected product: [UNKNOWN] dnsdist. 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-2018-14663/ (Markdown: https://insights.sbomify.com/CVE-2018-14663/index.md)
```

## Sources

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

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