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 2 September 2020.
- Which products and versions are affected?
- harp (npm) SEMVER:introduced=0.
- Is there a fix for This vulnerability?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is This vulnerability attacked?
- It is attacked with local access, in a software library.
- Am I affected?
- Check whether you run harp (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.
Technical details
The vulnerability is a cross-site scripting (XSS) flaw in harp's HTML rendering engine. The root cause is the failure to sanitize HTML output when processing files, allowing attackers to inject arbitrary JavaScript that executes in the context of clients. The attack requires the ability to place or influence malicious files on a server running harp; no network-level authentication bypass is needed, but the attacker must have file control or influence over harp's input. All versions of harp are reported affected. The advisory was withdrawn in 2021 by the maintainer on the grounds that, as a static web server, an XSS classification was deemed inappropriate—suggesting the vulnerability may have been misclassified or the risk reconsidered.
Affected products
- harp harp all versions
Timeline
- 2020-09-02: disclosed
- 2021-06-01: other: Advisory withdrawn by maintainer