follow-redirects is a Node.js HTTP and HTTPS client wrapper that automatically follows redirects. From 1.16.0 until 1.16.1, escapeRegex leaves valid header-name metacharacters unescaped in sensitiveHeaders. When an application declares a sensitive header whose name contains ^ or | and follows a cross-origin or HTTPS-to-HTTP redirect, unescaped regular-expression metacharacters prevent the generated filter from matching the declared header name, and the credential header is forwarded to an attacker-controlled redirect target. This issue is fixed in version 1.16.1.
Weakness
The product specifies a regular expression in a way that causes data to be improperly matched or compared.
Affected Software
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Red Hat Hardened Images | RedHat | grafana12-4-main-12.4.13-0.3.hum1 | * |
| Red Hat Hardened Images | RedHat | grafana13-1-main-13.1.8-0.4.hum1 | * |
| Red Hat Hardened Images | RedHat | grafana13-2-main-13.2.4-0.3.hum1 | * |
Potential Mitigations
Related Attack Patterns
- https://cwe.mitre.org/data/definitions/15.html
- https://cwe.mitre.org/data/definitions/6.html
- https://cwe.mitre.org/data/definitions/79.html
References
- https://github.com/follow-redirects/follow-redirects/commit/080a76d0e125b37bf81717368a61d5dc37aa56c8
- https://github.com/follow-redirects/follow-redirects/releases/tag/v1.16.1
- https://github.com/follow-redirects/follow-redirects/security/advisories/GHSA-8r9p-f939-6h3c
- https://github.com/follow-redirects/follow-redirects/security/advisories/GHSA-8r9p-f939-6h3c