Quick answers
- Is This vulnerability exploited in the wild?
- No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.
- How severe is This vulnerability?
- Informational severity, published 19 August 2020.
- Which products and versions are affected?
- ecstatic (npm) SEMVER:introduced=0,fixed=2.2.2.
- Is there a fix for This vulnerability?
- Yes. ecstatic (npm): upgrade to 2.2.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is This vulnerability attacked?
- It is attacked over the network.
- Am I affected?
- Check whether you run ecstatic (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- ecstatic (npm): upgrade to 2.2.2 or later
npm install ecstatic@2.2.2
Technical details
The vulnerability is an open redirect flaw in ecstatic's request handling logic. The exact root cause involves insufficient validation of redirect paths, allowing an attacker to craft URLs that cause the application to redirect users to external attacker-controlled sites. The attack requires only network access and a crafted URL—no authentication or user interaction beyond clicking a link is needed. An attacker can exploit this to redirect legitimate users from a trusted source to a malicious site for phishing or malware distribution. The issue was fixed in versions 2.2.2 (for 0–2.x track), 3.3.2 (for 3.x track), and 4.1.2 (for 4.x track).
Affected products
- ecstatic ecstatic < 2.2.2; 3.0.0 - < 3.3.2; 4.0.0 - < 4.1.2
Timeline
- 2020-08-19: disclosed