Exposure of Sensitive Information in simple-get
In versions of simple-get prior to 4.0.1, 3.1.1, and 2.8.2, when fetching a remote url with a cookie location response, headers will be followed, potentially resulting in an exposure of the session cookie to a third party.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2022-0355US | high7.5 | — | ||
Improper Removal of Sensitive Information Before Storage or Transfer in NPM simple-get prior to 4.0.1. | ||||
02
references
External citations — patches, advisories, analysis.
- https://github.com/feross/simple-getWEB
- https://github.com/feross/simple-get/commit/e4af095e06cd69a9235013e8507e220a79b9684fWEB
- https://github.com/feross/simple-get/pull/75#issuecomment-1027755026WEB
- https://github.com/feross/simple-get/pull/76#issuecomment-1027754710WEB
- https://huntr.dev/bounties/42c79c23-6646-46c4-871d-219c0d4b4e31WEB
- https://nvd.nist.gov/vuln/detail/CVE-2022-0355ADVISORY
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan