Loading vulnerability…
CVE-2022-0235 is an information-disclosure vulnerability in node-fetch redirect handling. When node-fetch follows a redirect from an initial request to a third-party domain, it can forward sensitive headers from the original request to the redirected destination. Exposed headers can include Authorization, WWW-Authenticate, and Cookie values. A redirect target controlled by an untrusted party can therefore receive credentials, session tokens, or other sensitive request metadata intended only for the original destination.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
20 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
An information-exposure vulnerability in node-fetch, allowing sensitive information to be exposed to an unauthorized actor, fixed in the OpenShift Container Platform update.
Exposure of sensitive information to an unauthorized actor in node-fetch.
An exposure-of-sensitive-information vulnerability in node-fetch.
Sensitive-information exposure vulnerability in node-fetch.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.