Quick answers
- Is CVE-2019-5416 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2019-5416 being exploited in the wild.
- How severe is CVE-2019-5416?
- Low severity, with a CVSS score of 3, published 25 March 2019.
- Which products and versions are affected?
- localhost-now (npm) up to 1.0.2.
- Is there a fix for CVE-2019-5416?
- 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 CVE-2019-5416 attacked?
- It is attacked over the network.
- Am I affected by CVE-2019-5416?
- Check whether you run localhost-now (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
localhost-now contains a path traversal vulnerability (CWE-22) due to insufficient URL sanitization. An unauthenticated attacker can exploit this over the network by sending requests with relative paths (e.g., "/../../../etc/passwd") to access files outside the configured served directory. No authentication or user interaction is required. The vulnerability affects all versions up to and including 1.0.2, with no fix currently available according to the advisory.
Affected products
- npm localhost-now up to 1.0.2
Identifiers
- CVE-2019-5416
- GHSA-qwj8-p662-3m7x
Timeline
- 2019-03-25: disclosed
- 2019: other: CVE-2019-5416 assigned