# CVE-2019-3871: Server-side request forgery in pdns

> Remote attackers can trigger Server-Side Request Forgery in PowerDNS Authoritative Server, causing denial of service or potential information disclosure via internal endpoint connections.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 21 Mar 2019
- **Updated:** 4 Aug 2024
- **Also known as:** DEBIAN-CVE-2019-3871, DLA-1737-1, DSA-4424-1, GHSA-mg3r-wf83-7hqh, MGASA-2019-0122, UBUNTU-CVE-2019-3871, openSUSE-SU-2019:1128-1

## What is CVE-2019-3871?

CVE-2019-3871 is a medium-severity server-side request forgery vulnerability in Fedoraproject Fedora, published on 21 Mar 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2019-3871?

It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `pdns` | SUSE:Package Hub 12 SP1 | All versions | 4.1.2-bp150.2.6.1 |
| `pdns` | SUSE:Package Hub 15 | All versions | 4.1.2-bp150.2.6.1 |
| `pdns` | openSUSE:Leap 15.0 | All versions | 4.1.2-bp150.2.6.1 |

Products: Fedoraproject Fedora, Powerdns Authoritative Server.

## How do I fix CVE-2019-3871?

Upgrade to a fixed version.

## Is CVE-2019-3871 being exploited?

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

## Other vulnerabilities in Fedoraproject Fedora

- [CVE-2024-4577](https://insights.sbomify.com/CVE-2024-4577/): PHP-CGI OS Command Injection (critical 9.8, exploited in the wild)
- [CVE-2021-39226](https://insights.sbomify.com/CVE-2021-39226/): Grafana Authentication Bypass (critical 9.8, exploited in the wild)
- [CVE-2019-5544](https://insights.sbomify.com/CVE-2019-5544/): VMware ESXi and Horizon DaaS OpenSLP Heap-Based Buffer Overflow (critical 9.8, exploited in the wild)
- [CVE-2024-4947](https://insights.sbomify.com/CVE-2024-4947/): Google Chromium V8 Type Confusion (critical 9.6, exploited in the wild)
- [CVE-2024-4671](https://insights.sbomify.com/CVE-2024-4671/): Google Chromium Visuals Use-After-Free (critical 9.6, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-3871 and fix it if it is affected.

What it is: CVE-2019-3871 is a medium-severity server-side request forgery vulnerability in Fedoraproject Fedora, published on 21 Mar 2019. 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-2019-3871 in the wild and no public exploit code.

Affected product: Fedoraproject Fedora. 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-2019-3871/ (Markdown: https://insights.sbomify.com/CVE-2019-3871/index.md)
```

## Sources

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

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