Skip to main content
No exploitation reportedFix available

CVE-2018-14663

No exploitation reported by the sources we read.

  • Published2018-11-26
  • WeaknessCWE-20

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

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.

Timeline

dates in UTC
  1. 2018-11-2623:29CVE publishedNVD

Versions per branch

NVD
Powerdns dnsdist
BranchAffectedFixed in
1.3≤ 1.3.2no fix published

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • dnsdistUbuntu:Pro:18.04:LTSall versions · no fixed version listed
  • dnsdistUbuntu:16.04:LTSall versions · no fixed version listed
  • dnsdistSUSE:Linux Enterprise Server for SAP Applications 15 SP2all versions · fixed in 1.8.0-150100.3.5.1
  • dnsdistSUSE:Linux Enterprise Server for SAP Applications 15 SP1all versions · fixed in 1.8.0-150100.3.5.1
  • dnsdistSUSE:Linux Enterprise Server 15 SP3-LTSSall versions · fixed in 1.8.0-150100.3.5.1
  • dnsdistSUSE:Linux Enterprise Server 15 SP2-LTSSall versions · fixed in 1.8.0-150100.3.5.1
  • dnsdistSUSE:Linux Enterprise Server 15 SP1-LTSSall versions · fixed in 1.8.0-150100.3.5.1
  • dnsdistSUSE:Linux Enterprise Module for Basesystem 15 SP5all versions · fixed in 1.8.0-150400.9.3.1

15 more package ranges on OSV.dev

Full record on NVD

Fix

Advisories and patches

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

  • CNACVSS 3.05.9known since 2026-10-23
  • NVDCVSS 3.05.9read 2026-10-23
  • NVDCVSS 2.04.3read 2026-10-23
  • CNAweakness (CWE)CWE-20known since 2026-10-23
  • NVDweakness (CWE)CWE-20read 2026-10-23
  • FIRST EPSSEPSS score2.6 %2026-11-18
  • OSVaffected packages—
  • GitHub Advisoriesadvisory—

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N
Published
2018-11-26
Last Modified
2026-06-17
NVD status
Modified
GitHub Advisory
GHSA-r2j7-9v32-854m

Frequently asked questions

What is CVE-2018-14663?

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.

Is CVE-2018-14663 actively exploited?

Active exploitation of CVE-2018-14663 has not been confirmed. Its EPSS score was 2.6% on 2026-11-18, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2018-14663?

CVE-2018-14663 has a CVSS v3 base score of 5.9 (MEDIUM severity), with vector string CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N.

Running luajit? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month

Sources for this record