GHSA-6J6F-FH7W-VVJR
HTTP header allowlist (`allowedHeaders`) could be bypassed by using a shared preset
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:L/A:N
Fuente: GitHub
Ciclo de vida de la vulnerabilidad
| Fecha | Fase | Evento | Detalle |
|---|---|---|---|
| Divulgación | Publicada | GHSA-6J6F-FH7W-VVJR divulgada · CVSS 7.1 (GitHub) | |
| Divulgación | Modificada | Última actualización del registro | |
| Monitoreo | Detectada | Ingresó al índice | |
| Monitoreo | Verificada | Última verificación contra las fuentes |
When Renovate interacts over HTTP with external services, an allowlist is used for any HTTP headers that are included in the requests.
Part of this is controlled by a self-hosted administrator, using the `allowedHeaders` https://docs.renovatebot.com/self-hosted-configuration/#allowedheaders configuration, which then allows a repository to specify i.e.:
{
"$schema": "https://docs.renovatebot.com/renovate-schema.json",
"hostRules": [
{
"matchHost": "https://domain.com/all-versions",
"headers": {
"Authorization": "Bearer {{ secrets.ALL_VERSIONS_SECRET }}"
}
}
]
}It was previously possible for a repository to bypass this requirement by including the `hostRules` entry inside a shared preset, where the `headers` would not be validated.
Impact
- You are a self-hosted administrator
- You restrict the HTTP headers that a user can specify
- Renovate's default is `allowedHeaders: ["X-*"]`, so you are likely already restricting these
- You have users who use presets
- One of those presets specifies `hostRules[].headers` inside them
> [!CAUTION]
> Because these presets can also be externally sourced, this could allow a preset from the public Internet (or internal to users in your deployment) to inject in custom HTTP headers to different hosts.
>
> Although additional information would be needed to employ a targeted attack, this is still a significant risk.
Patches
This is patched in Renovate 44.60.1 https://github.com/renovatebot/renovate/releases/tag/44.60.1.
For self-hosted administrators setting `headers`
Self-hosted administrators who set `headers` on requests are recommended to upgrade to 44.119.0 https://github.com/renovatebot/renovate/releases/tag/44.119.0.
Prior to this version, Renovate would require that a self-hosted administrator who sets `headers` would need to allowlist them via `allowedHeaders`, allowing any users on their deployment to also set those headers.
This is no longer the case as of 44.119.0, where the administrator's `headers` are implicitly allowed, similar to how `allowedEnv` works.
Upgrading will allow the self-hosted administrator to reduce the allowlist in `allowedHeaders` to only names that they expect their users to override.
Workarounds
None
AI Disclosure
This GHSA was discovered using Scrutineer https://github.com/alpha-omega-security/scrutineer/, using the following models:
- Claude Fable 5 (discovery)
This was reviewed by 1+ human, and the fixes prepared with a human, and potentially some AI support.
This disclosure itself is human written and human reviewed.
Desglose de métricas
Rangos afectados
Estado del parche por paquete
| Paquete / producto | Estado | Corregida en | Desde divulgación | Última versión |
|---|---|---|---|---|
npmrenovate |
Corregida | 44.60.1 | — | 44.239.1 no afectada |
44.60.1Arsenal público
Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.
https://github.com/renovatebot/renovate/security/advisories/GHSA-6j6f-fh7w-vvjrLas referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.
