phin may include sensitive headers in subsequent requests after redirect

published 2024-04-11 2y ago modified 2024-04-11 2y ago

cvss: 4.3; version 3.1, GitHub
cisa kev: Not listed; not in CISA's catalog
epss: —; no score, EPSS covers CVEs only
public exploits: 0; none known

### Impact

Users may be impacted if sending requests including sensitive data in specific headers with `followRedirects` enabled.

### Patches

The [follow-redirects](https://github.com/follow-redirects/follow-redirects) library is now being used for redirects and removes some headers that may contain sensitive information in some situations.

### Workarounds

N/A. Please update to resolve the issue.

Patch / fix

fixed in 1 links 1

npm phin 3.7.1

github.com/ethanent/phin@c071f95 commit

Is GHSA-x565-32qp-m3vf in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CVSS scores

assigned by	version	score	vector
GitHub	3.1	4.3	CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N

Affected packages

ecosystem	package	affected	fixed in
npm	phin	<3.7.1	3.7.1

Classification

Weakness

CWE-200 Exposure of Sensitive Information to an Unauthorized Actor

References

Sources

GitHub Advisory GHSA-x565-32qp-m3vf

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.