Pi-hole FTL: CRLF Injection / HTTP Header Injection via Group Name
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.370% probability within 30 days)
| 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 |
|---|---|---|
| Metrics |
ssvc
|
| 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.0 until 6.7, validation in src/api/list.c permits spaces for GRAVITY_GROUPS and consequently skips carriage-return and line-feed validation for group names submitted through POST /api/groups. The unsanitized name is copied into the Location value in pi_hole_extra_headers, and CivetWeb interprets embedded CR/LF sequences as separate HTTP response headers. An authenticated administrator can therefore inject headers such as Set-Cookie, Location, or Cache-Control; when a browser processes the response, this can cause session fixation, attacker-controlled redirects, or cache behavior changes. This issue is fixed in version 6.7. | |
| Title | Pi-hole FTL: CRLF Injection / HTTP Header Injection via Group Name | |
| Weaknesses | CWE-113 | |
| References |
| |
| Metrics |
cvssV3_1
|