Pi-hole FTL: Remote Code Execution (RCE) via CivetWeb Configuration Injection
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| pi-hole | FTL | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Pi-hole | Ftl |
|
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.747% probability within 30 days)
Key SSVC decision points have not yet been added.
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Pi-hole
Pi-hole ftl |
|
| Vendors & Products |
Pi-hole
Pi-hole ftl |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Pi-hole FTL is the core engine of the Pi-hole network-level advertisement and tracker blocker. From 6.6.2 until 6.7, PATCH /api/config accepts unfiltered CivetWeb lua_* options through webserver.advancedOpts, while POST /api/teleporter writes attacker-controlled content from a dhcp.leases archive entry through src/zip/teleporter.c without content validation. An authenticated administrator can place controlled file content on disk, point a Lua execution option at that file, and rely on the advancedOpts configuration change to restart FTL. CivetWeb then executes the file as Lua through the processing in src/webserver/webserver.c, allowing arbitrary commands to run as the pihole operating-system user and persist across restarts while the configuration and file remain. This issue is fixed in version 6.7. | |
| Title | Pi-hole FTL: Remote Code Execution (RCE) via CivetWeb Configuration Injection | |
| Weaknesses | CWE-15 CWE-20 |
|
| References |
| |
| Metrics |
cvssV3_1
|