Server crash via unencoded redirect header
Published Jan 2, 2020 · Updated Aug 4, 2024
Denial of service in Ecstatic Project ecstatic before 4.1.3 allows remote attackers to crash the server via a crafted URL. The directory-redirect path copied an unencoded form-feed character from the request URL into the HTTP Location header, causing Node.js setHeader to throw a TypeError. A reachable server and an existing directory path are sufficient; no authentication or user interaction is required, and the affected process terminates.
Summary
What happened
Denial of service in Ecstatic Project ecstatic before 4.1.3 allows remote attackers to crash the server via a crafted URL. The directory-redirect path copied an unencoded form-feed character from the request URL into the HTTP Location header, causing Node.js setHeader to throw a TypeError. A reachable server and an existing directory path are sufficient; no authentication or user interaction is required, and the affected process terminates.
The record
- CVE
- CVE-2019-10775
- Published
- Jan 2, 2020
- Updated
- Aug 4, 2024
- Vendor
- Ecstatic Project
- Product
- ecstatic
- Classifications
- CWE-400, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 2, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=All versions
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- Crafted form-feed redirect requestproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo