Approved changes feed: RSS · Atom
cpe:2.3:a:hapijs:wreck:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Hapijs (cde07e56-6e3e-5211-9d96-925613bfc13f) |
|---|---|
| Product | Wreck (1d227556-b8b8-5781-97b6-79ed570db05b) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-48022 |
vulnerable | 2026-07-29 00:55:01.041424 |
@hapi/wreck: Sensitive credential headers leak across cross-port and cross-scheme redirects
MEDIUM (6.5)
@hapi/wreck is an HTTP client utility. Prior to 18.1.2, Wreck strips credential headers including Authorization, Cookie, and Proxy-Authorization before following a cross-origin redirect, but the origin check compares hostnames only and ignores scheme and port, so credentials are forwarded intact across same-host port changes and HTTPS-to-HTTP downgrades, allowing a co-tenant on an adjacent port or a network-position attacker capable of forging a redirect to capture bearer tokens, session cookies, and proxy credentials and impersonate the victim against the upstream service. This issue is fixed in version 18.1.2.
Published: 2026-07-17T21:02:05.980Z
Updated: 2026-07-20T19:10:59.345Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-44979 |
vulnerable | 2026-07-29 00:52:14.968182 |
@hapi/wreck : Sensitive `Proxy-Authorization` header leaked across cross-hostname redirects
@hapi/wreck is an HTTP client utility. Prior to 18.1.1, when @hapi/wreck follows a 3xx redirect to a different hostname, only the Authorization and Cookie headers are stripped, and the standard credential header Proxy-Authorization is forwarded intact to the redirect target, potentially exposing forward-proxy credentials to a host outside the original trust boundary when redirects are enabled through the redirects option or Wreck.defaults({ redirects: ... }). This issue is fixed in version 18.1.1.
Published: 2026-07-17T21:01:01.165Z
Updated: 2026-07-20T14:35:45.343Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.