Quick answers
- Is CVE-2019-5423 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2019-5423 being exploited in the wild.
- How severe is CVE-2019-5423?
- Informational severity, with a CVSS score of 7.5, published 8 April 2019.
- Which products and versions are affected?
- http-live-simulator (npm) SEMVER:introduced=0,fixed=1.0.6.
- Is there a fix for CVE-2019-5423?
- Yes. http-live-simulator (npm): upgrade to 1.0.6 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2019-5423 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2019-5423?
- Check whether you run http-live-simulator (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
- http-live-simulator (npm): upgrade to 1.0.6 or later
npm install http-live-simulator@1.0.6
Technical details
A path traversal vulnerability (CWE-22) exists in http-live-simulator versions prior to 1.0.6. The root cause is insufficient sanitization of user-provided input used to construct file paths. A remote, unauthenticated attacker can exploit this by using relative path sequences (e.g., '../') in HTTP requests to escape the intended directory and read arbitrary files from the underlying file system. The vulnerability is fixed in version 1.0.6.
Affected products
- http-live-simulator project http-live-simulator < 1.0.6
Identifiers
- CVE-2019-5423
- GHSA-2hhw-p8mg-jrm6
Timeline
- 2019-04-03: advisory: NVD published date
- 2019-04-08: disclosed: GitHub Advisory Database publication