Quick answers
- Is CVE-2019-10775 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2019-10775 being exploited in the wild.
- How severe is CVE-2019-10775?
- Informational severity, with a CVSS score of 7.5, published 15 December 2020.
- Which products and versions are affected?
- ecstatic (npm) SEMVER:introduced=0,fixed=4.1.3.
- Is there a fix for CVE-2019-10775?
- Yes. ecstatic (npm): upgrade to 4.1.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2019-10775 attacked?
- It is attacked over the network.
- Am I affected by CVE-2019-10775?
- 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 4.1.3 or later
npm install ecstatic@4.1.3
Technical details
The vulnerability exists in ecstatic's URL parameter parsing during redirect handling. When processing requests with certain URL parameters (specifically containing invalid characters like \x0c), the library attempts to redirect the URL but fails to properly sanitize the input, resulting in a TypeError when invalid header characters are included in the response. The vulnerability is triggered via a network request and requires no authentication. An attacker can exploit this by sending a crafted URL (e.g., with a form-feed character in the query string) to crash the application. The issue is tracked as CWE-400 (uncontrolled resource consumption). Patched versions 4.1.3 and later address this vulnerability.
Affected products
- ecstatic ecstatic <4.1.3
Identifiers
- CVE-2019-10775
- GHSA-jc84-3g44-wf2q
Timeline
- 2019-12-31: disclosed
- 2020-12-15: advisory: GHSA advisory published