# CVE-2024-34361: Pi-hole Blind Server-Side Request Forgery (SSRF) vulnerability can lead to Remote Code Execution (RCE)

> An authenticated user can exploit SSRF in Pi-hole to make internal requests, potentially leading to remote code execution.

- **Severity:** High 8.6 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Jul 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-jg6g-rrj6-xfg6

## What is CVE-2024-34361?

CVE-2024-34361 is a high-severity server-side request forgery vulnerability in pi-hole, published on 5 Jul 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Pi-hole is a DNS sinkhole that protects devices from unwanted content without installing any client-side software. A vulnerability in versions prior to 5.18.3 allows an authenticated user to make internal requests to the server via the `gravity_DownloadBlocklistFromUrl()` function. Depending on some circumstances, the vulnerability could lead to remote command execution. Version 5.18.3 contains a patch for this issue.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2024-34361?

It affects 1 product.


Products: Pi-Hole Pi-Hole.

## How do I fix CVE-2024-34361?

No fix has been published for CVE-2024-34361 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-34361 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-34361 exists.

Public exploit code:

- This repository contains an exploit for CVE-2024-34361, a critical Pi-hole vulnerability (CVSS 8.6). It uses SSRF to achieve RCE by exploiting improper URL validation, allowing attackers to send arbitrary requests and execute commands on the system.  Disclaimer: For educational and ethical security testing only. Unauthorized use is illegal. (github_poc): https://github.com/T0X1Cx/CVE-2024-34361-Pi-Hole-SSRF-to-RCE

## Other vulnerabilities in pi-hole

- [CVE-2020-8816](https://insights.sbomify.com/CVE-2020-8816/): Pi-Hole AdminLTE Remote Code Execution (critical 9.1, exploited in the wild)
- [CVE-2025-34087](https://insights.sbomify.com/CVE-2025-34087/): Pi-Hole AdminLTE Whitelist (now 'Web Allowlist') Remote Command Execution (critical 9.0)
- [CVE-2026-50130](https://insights.sbomify.com/CVE-2026-50130/): Pi-hole: Local privilege escalation from `pihole` user to root via `/etc/pihole/logrotate` (high 8.8)
- [CVE-2020-11108](https://insights.sbomify.com/CVE-2020-11108/): File upload in n/a (high 8.8)
- [CVE-2019-13051](https://insights.sbomify.com/CVE-2019-13051/): Pi-Hole 4.3 allows Command Injection. (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-34361 and fix it if it is affected.

What it is: CVE-2024-34361 is a high-severity server-side request forgery vulnerability in pi-hole, published on 5 Jul 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-34361 exists.

Affected product: pi-hole. 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-2024-34361/ (Markdown: https://insights.sbomify.com/CVE-2024-34361/index.md)
```

## Sources

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

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