Technical impact
Pi‑hole’s gravity.sh script checks whether a file:// adlist is readable by running a test as the pihole user, but later uses curl, often running as root, to normalize the URL and open a file. When the adlist points to a path that is readable by the pihole user yet resolves to a different file when accessed as root, a process can bypass the read check and access a root‑only file. The flaw, identified as CWE‑59, allows an attacker with the ability to add adlists and place symlinks or decoy files on the host to read data intended for privileged processes, potentially leaking sensitive information or enabling further exploitation. Affected systems include the open‑source Pi‑hole DNS sinkhole. The problem exists in all versions of Pi‑hole prior to 6.5; version 6.5 and later contain a fix that prevents the curl‑based resolution mismatch. Only installations that run gravity.sh as the pihole user but allow curl to run as root are susceptible. Risk and exploitability are low from a public safety perspective: the CVSS score is 2.2, EPSS data are not available, and it is not listed in the CISA KEV catalog. However, exploitation requires local administrative rights to add adlists and create symlinks. The most likely attack vector is a local attacker who has exploited another vulnerability or has compromised the Pi‑hole server. Given these constraints, the attack can be mitigated by deploying the vendor‑issued update and by restricting adlist configuration to trusted users.
Affected Systems
The vulnerability affects the Pi‑hole DNS sinkhole service from the Pi‑hole project. All releases older than version 6.5 are vulnerable; version 6.5 and later do not contain the flaw.
Risk and Exploitability
The CVSS score of 2.2 indicates a low severity. The EPSS score is currently not available, and the vulnerability is not listed in the CISA KEV catalog. Attackers would need administrative or privileged access to the Pi‑hole server to add adlists, create symbolic links, and place decoy files. In that scenario, curl run as root could resolve the path to a privileged file after the read check has passed, allowing the attacker to read data that should be protected.