GHSA-cxjh-pqwp-8mfp

Source

https://github.com/advisories/GHSA-cxjh-pqwp-8mfp

Import Source

https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2024/03/GHSA-cxjh-pqwp-8mfp/GHSA-cxjh-pqwp-8mfp.json

JSON Data

https://api.osv.dev/v1/vulns/GHSA-cxjh-pqwp-8mfp

Aliases

CVE-2024-28849

Related

Published

2024-03-14T17:19:42Z

Modified

2024-04-02T17:54:20Z

Severity

6.5 (Medium) CVSS_V3 - CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N CVSS Calculator

Summary

follow-redirects' Proxy-Authorization header kept across hosts

Details

When using axios, its dependency follow-redirects only clears authorization header during cross-domain redirect, but allows the proxy-authentication header which contains credentials too.

Steps To Reproduce & PoC

Test code:

const axios = require('axios');

axios.get('http://127.0.0.1:10081/', {
 headers: {
 'AuThorization': 'Rear Test',
 'ProXy-AuthoriZation': 'Rear Test',
 'coOkie': 't=1'
 }
})
 .then((response) => {
 console.log(response);
 })

When I meet the cross-domain redirect, the sensitive headers like authorization and cookie are cleared, but proxy-authentication header is kept.

Impact

This vulnerability may lead to credentials leak.

Recommendations

Remove proxy-authentication header during cross-domain redirect

Recommended Patch

follow-redirects/index.js:464

- removeMatchingHeaders(/^(?:authorization|cookie)$/i, this._options.headers);
+ removeMatchingHeaders(/^(?:authorization|proxy-authorization|cookie)$/i, this._options.headers);

Database specific

{
    "nvd_published_at": "2024-03-14T17:15:52Z",
    "cwe_ids": [
        "CWE-200"
    ],
    "severity": "MODERATE",
    "github_reviewed": true,
    "github_reviewed_at": "2024-03-14T17:19:42Z"
}

References

Affected packages

npm / follow-redirects

Package

Name: follow-redirects; View open source insights on deps.dev
Purl: pkg:npm/follow-redirects

Affected ranges

Type: SEMVER
Events: Introduced

0Unknown introduced version / All previous versions are affected

Fixed

1.15.6

Database specific

{
    "last_known_affected_version_range": "<= 1.15.5"
}