A vulnerability was found in PowerDNS Authoritative Server before 4.0.7 and before 4.1.7. An insufficient validation of data coming from the user when building a HTTP request from a DNS query in the HTTP Connector of the Remote backend, allowing a remote user to cause a denial of service by making the server connect to an invalid endpoint, or possibly information disclosure by making the server connect to an internal endpoint and somehow extracting meaningful information about the response

- Update to 4.1.7

Release notes:
https://doc.powerdns.com/authoritative/changelog/4.1.html#change-4.1.7

Security Advisory:
https://doc.powerdns.com/authoritative/security-advisories/powerdns-ad visory-2019-03.html

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.

Adam Dobrawy, Frederico Silva and Gregory Brzeski from HyperOne.com discovered that pdns, an authoritative DNS server, did not properly validate user-supplied data when building a HTTP request from a DNS query in the HTTP Connector of the Remote backend. This would allow a remote user to cause either a denial-of-service, or information disclosure.

This update for pdns fixes the following issue :

Security issue fixed :

  - CVE-2019-3871: Fixed an insufficient validation in the     HTTP remote backend which could allow a remote user to     cause the HTTP backend to connect to an     attacker-specified host instead of the configured one     (bsc#1129734).

A vulnerability was found in PowerDNS Authoritative Server before 4.0.7 and before 4.1.7. An insufficient validation of data coming from the user when building a HTTP request from a DNS query in the HTTP Connector of the Remote backend, allowing a remote user to cause a denial of service by making the server connect to an invalid endpoint, or possibly information disclosure by making the server connect to an internal endpoint and somehow extracting meaningful information about the response.

Only installations using the pdns-backend-remote package are affected.

For Debian 8 'Jessie', this problem has been fixed in version 3.4.1-4+deb8u9.

We recommend that you upgrade your pdns packages.

NOTE: Tenable Network Security has extracted the preceding description block directly from the DLA security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

PowerDNS developers report :

An issue has been found in PowerDNS Authoritative Server when the HTTP remote backend is used in RESTful mode (without post=1 set), allowing a remote user to cause the HTTP backend to connect to an attacker-specified host instead of the configured one, via a crafted DNS query. This can be used to cause a denial of service by preventing the remote backend from getting a response, content spoofing if the attacker can time its own query so that subsequent queries will use an attacker-controlled HTTP server instead of the configured one, and possibly information disclosure if the Authoritative Server has access to internal servers.

ID	Name	Product	Family	Severity
124484	Fedora 30 : pdns (2019-2fca900a42)	Nessus	Fedora Local Security Checks	high
123758	Debian DSA-4424-1 : pdns - security update	Nessus	Debian Local Security Checks	high
123670	openSUSE Security Update : pdns (openSUSE-2019-1128)	Nessus	SuSE Local Security Checks	high
123524	Debian DLA-1737-1 : pdns security update	Nessus	Debian Local Security Checks	high
123143	Fedora 28 : pdns (2019-b85d4171d4)	Nessus	Fedora Local Security Checks	high
123141	Fedora 29 : pdns (2019-9993d32c48)	Nessus	Fedora Local Security Checks	high
122960	FreeBSD : PowerDNS -- Insufficient validation in the HTTP remote backend (6001cfc6-9f0f-4fae-9b4f-9b8fae001425)	Nessus	FreeBSD Local Security Checks	high

Detections

Analytics

CVE-2019-3871

high

Tenable Plugins

high

high

high

high

high

high

high