GHSA-PG8V-XW58-FRQ8
Grav bundled IIS web.config (and lighttpd.conf) case-sensitive deny rules allow case-variation bypass and sensitive file disclosure
Texto original en inglés · Ver en español
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Fuente: GitHub
Ciclo de vida de la vulnerabilidad
| Fecha | Fase | Evento | Detalle |
|---|---|---|---|
| Divulgación | Publicada | GHSA-PG8V-XW58-FRQ8 divulgada · CVSS 7.5 (GitHub) | |
| Monitoreo | Detectada | Ingresó al índice | |
| Monitoreo | Verificada | Última verificación contra las fuentes |
Summary
The web server configs Grav bundles for IIS (`webserver-configs/web.config`) match all of their access-control deny rules case-sensitively. IIS URL Rewrite `<match>` elements default to `ignoreCase="true"`, but every deny rule in the shipped `web.config` sets `ignoreCase="false"`, making the regexes case-sensitive.
On IIS, which runs on Windows where NTFS is case-insensitive, an unauthenticated attacker can vary the case of the folder or file extension — for example `GET /user/CONFIG/system.YAML` — so that no deny rule matches, and the IIS static file handler resolves and returns the underlying file.
This is the IIS sibling of CVE-2026-62673 (GHSA-vwg3-w8w3-pc79). That fix added `[NC]` to the Apache `.htaccess` rules and the `ui` flag to `system/router.php`, and the shipped `nginx.conf` (`~*`) and `Caddyfile` (`(?i)`) were already case-insensitive — but the IIS `web.config` was never updated.
The same class of gap exists in `webserver-configs/lighttpd.conf`, whose `user/(config|env)`, directory, script-extension, root-file and dotfile rules lack the `(?i)` modifier (the `user/accounts` and `user/data` rules already have it). lighttpd is far lower risk in practice because it almost always runs on a case-sensitive Linux filesystem.
Affected versions
getgrav/grav through 2.0.24, for deployments served by the bundled `webserver-configs/web.config` (IIS) and, as a lower-severity sibling, `lighttpd.conf`.
Apache (`.htaccess`), nginx, Caddy and the PHP built-in server are not affected. The `.htaccess` installer heal does not touch `web.config` or `lighttpd.conf`, so operators must re-copy the corrected sample after upgrading.
Details
The deny rules in `web.config` — `user_sensitive_folders`, `user_accounts`, `user_data`, `user_error_redirect`, `user_pages`, `system`, `vendor` and `ignore_folders` — each carry `ignoreCase="false"`:
<rule name="user_sensitive_folders" stopProcessing="true">
<match url="^user/(config|env)/(.*)" ignoreCase="false" />
<action type="Redirect" url="error" redirectType="Permanent" />
</rule>
Because these are URL Rewrite `<match>` regexes, and not `<requestFiltering>` elements (which are case-insensitive unconditionally), there is no case-insensitive fallback.
A request for `/user/CONFIG/system.YAML` fails every case-sensitive deny rule. The initial `request_filename` rewrite-to-index.php rule also does not fire, because `{REQUEST_FILENAME}` resolves as an existing file on case-insensitive NTFS. IIS then serves the file.
Proof of concept
GET /user/CONFIG/system.YAML HTTP/1.1
Host: TARGET
Lowercase control, correctly blocked with a 301 to /error:
GET /user/config/system.yaml HTTP/1.1
Host: TARGET
Scope note on MIME registration
The IIS static handler serves only registered MIME types. `.json` is registered by default and leaks outright. `.yaml` and `.yml` return HTTP 404.3 on a stock IIS unless a YAML MIME mapping has been added, which is common where operators serve config or OpenAPI files. The deny-rule bypass itself is unconditional; whether a given file is then returned depends on its extension's MIME registration.
Impact
An unauthenticated attacker on an IIS-served Grav site can request sensitive files whose extension IIS serves — `user/config/*.yaml` (`security.salt` and the API/JWT secret), `user/config/plugins/*.yaml` (plugin credentials such as SMTP), and `user/accounts/*.yaml` (password hashes) — bypassing the deny rules through case variation. This crosses Grav's trust boundary: an anonymous visitor reaches server-side secret files.
Patches
Fixed by setting `ignoreCase="true"` on all deny rules in `webserver-configs/web.config`, and by adding the `(?i)` modifier to the case-sensitive deny rules in `webserver-configs/lighttpd.conf`, bringing both to parity with the Apache, nginx, Caddy and PHP-router rules.
IIS and lighttpd operators must re-copy the updated sample config, as the `.htaccess` upgrade heal does not modify them.
Credits
Reported by @movon-ava.
Incluye detalles técnicos publicados por el investigador. Úselos solo para validar y corregir sus propios sistemas.
Desglose de métricas
Rangos afectados
Estado del parche por paquete
| Paquete / producto | Estado | Corregida en | Desde divulgación | Última versión |
|---|---|---|---|---|
Packagistgetgrav/grav |
Corregida | 1.7.53.8, 2.0.25 | — | — |
1.7.53.82.0.25Arsenal público
Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.
https://github.com/getgrav/grav/security/advisories/GHSA-pg8v-xw58-frq8Las referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.
