Exposure of Sensitive Information in eventsource
When fetching an url with a link to an external site (Redirect), the users Cookies & Autorisation headers are leaked to the third party application. According to the same-origin-policy, the header should be "sanitized."
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2022-1650US | critical9.3 | — | ||
Improper Removal of Sensitive Information Before Storage or Transfer in GitHub repository eventsource/eventsource prior to v2.0.2. | ||||
02
references
External citations — patches, advisories, analysis.
- https://github.com/EventSource/eventsource/commit/f9f6416567bff62c1af2f4314be51d9870e94bc2WEB
- https://github.com/EventSource/eventsource/pull/273#issuecomment-1127624508WEB
- https://github.com/eventsource/eventsourcePACKAGE
- https://github.com/eventsource/eventsource/commit/10ee0c4881a6ba2fe65ec18ed195ac35889583c4WEB
- https://huntr.dev/bounties/dc9e467f-be5d-4945-867d-1044d27e9b8eWEB
- https://lists.debian.org/debian-lts-announce/2022/12/msg00021.htmlWEB
- https://nvd.nist.gov/vuln/detail/CVE-2022-1650ADVISORY
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