Excon: redact additional sensitive/risky headers when following redirects
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| excon | excon | affected |
|
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Excon | Excon |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-48rx-c7pg-q66r | Excon does not redact additional sensitive/risky headers when following redirects |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.427% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Excon
Excon excon |
|
| Vendors & Products |
Excon
Excon excon |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Excon is usable, fast, simple HTTP 1.1 for Ruby. Prior to 1.5.0, Excon's RedirectFollower middleware failed to strip additional sensitive headers when following redirects and did not provide a custom list of headers to strip. This could cause inadvertent leakage of sensitive data when the initial request includes header information that is not intended for the new target. This issue is fixed in version 1.5.0. | |
| Title | Excon: redact additional sensitive/risky headers when following redirects | |
| Weaknesses | CWE-201 | |
| References |
| |
| Metrics |
cvssV3_1
|