follow-redirects sensitiveHeaders regex escaping can expose credential headers
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| follow-redirects | follow-redirects | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Follow-redirects | Follow Redirects |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-8r9p-f939-6h3c | follow-redirects sensitiveHeaders regex escaping can expose credential headers |
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.471% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-212 | |
| References |
| |
| Metrics |
threat_severity
|
cvssV3_1
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Follow-redirects
Follow-redirects follow Redirects |
|
| Vendors & Products |
Follow-redirects
Follow-redirects follow Redirects |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | follow-redirects sensitiveHeaders regex escaping can expose credential headers | |
| Weaknesses | CWE-185 CWE-200 |
|
| References |
| |
| Metrics |
cvssV4_0
|