Quick answers
- Is CVE-2018-3809 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2018-3809 being exploited in the wild.
- How severe is CVE-2018-3809?
- Low severity, with a CVSS score of 3, published 18 July 2018.
- Which products and versions are affected?
- serve (npm) before 7.0.0.
- Is there a fix for CVE-2018-3809?
- 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-2018-3809 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2018-3809?
- Check whether you run serve (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 exists in serve versions before 7.0.0 and is rooted in a case-sensitivity bypass in the file access control logic. On case-insensitive file systems (such as NTFS and HFS+), an attacker can request files using alternate casing to circumvent the ignore security control that is intended to block access to sensitive files. The attack requires only network access to the serve HTTP endpoint and no authentication. An attacker can read file contents that should be restricted, leading to information disclosure. The fix is available in serve version 7.0.0 and later.
Affected products
- npm serve before 7.0.0
Identifiers
- CVE-2018-3809
- GHSA-686g-3xr3-x4x6
Timeline
- 2018-07-18: disclosed