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.

The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - 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.
    (CVE-2018-14663)

Note that Nessus relies on the presence of the package as reported by the vendor.

The remote SUSE Linux SLES15 / SLES_SAP15 host has a package installed that is affected by multiple vulnerabilities as referenced in the SUSE-SU-2023:2777-1 advisory.

  - An issue has been found in dnsdist before 1.2.0 in the way EDNS0 OPT records are handled when parsing     responses from a backend. When dnsdist is configured to add EDNS Client Subnet to a query, the response     may contain an EDNS0 OPT record that has to be removed before forwarding the response to the initial     client. On a 32-bit system, the pointer arithmetic used when parsing the received response to remove that     record might trigger an undefined behavior leading to a crash. (CVE-2016-7069)

  - dnsdist version 1.1.0 is vulnerable to a flaw in authentication mechanism for REST API potentially     allowing CSRF attack. (CVE-2017-7557)

  - 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.
    (CVE-2018-14663)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote openSUSE 15 host has packages installed that are affected by multiple vulnerabilities as referenced in the SUSE-SU-2023:2760-1 advisory.

  - An issue has been found in dnsdist before 1.2.0 in the way EDNS0 OPT records are handled when parsing     responses from a backend. When dnsdist is configured to add EDNS Client Subnet to a query, the response     may contain an EDNS0 OPT record that has to be removed before forwarding the response to the initial     client. On a 32-bit system, the pointer arithmetic used when parsing the received response to remove that     record might trigger an undefined behavior leading to a crash. (CVE-2016-7069)

  - dnsdist version 1.1.0 is vulnerable to a flaw in authentication mechanism for REST API potentially     allowing CSRF attack. (CVE-2017-7557)

  - 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.
    (CVE-2018-14663)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

Security fix for CVE-2018-14663

Note that Tenable Network Security has extracted the preceding description block directly from the Fedora update system website.
Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

ID	Name	Product	Family	Severity
257190	Linux Distros Unpatched Vulnerability : CVE-2018-14663	Nessus	Misc.	medium
177989	SUSE SLES15 Security Update : dnsdist (SUSE-SU-2023:2777-1)	Nessus	SuSE Local Security Checks	high
177917	openSUSE 15 Security Update : dnsdist (SUSE-SU-2023:2760-1)	Nessus	SuSE Local Security Checks	high
120889	Fedora 28 : dnsdist (2018-ef486b9e50)	Nessus	Fedora Local Security Checks	medium
120658	Fedora 29 : dnsdist (2018-9f375c6c01)	Nessus	Fedora Local Security Checks	medium

Detections

Analytics

CVE-2018-14663

medium

Tenable Plugins

medium

high

high

medium

medium