Quick answers
- Is CVE-2020-8135 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2020-8135 being exploited in the wild.
- How severe is CVE-2020-8135?
- Informational severity, with a CVSS score of 0, published 3 September 2020.
- Which products and versions are affected?
- @uppy/companion (npm) SEMVER:introduced=0,fixed=1.9.3; Uppy Companion prior to 1.9.3.
- Is there a fix for CVE-2020-8135?
- Yes. @uppy/companion (npm): upgrade to 1.9.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2020-8135 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2020-8135?
- Check whether you run @uppy/companion (npm) or Uppy Companion 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
- @uppy/companion (npm): upgrade to 1.9.3 or later
npm install @uppy/companion@1.9.3
Technical details
The vulnerability is a Server-Side Request Forgery (SSRF) in the GET route handler of @uppy/companion. The vulnerable code passes unsanitized user input from req.body.url directly to an HTTP GET request without validation or sanitization. An attacker can inject arbitrary URLs via the url parameter to make the server perform requests to internal IP addresses, private services, or other unintended targets. The attack requires network access to the companion server but no authentication. The vulnerability is fixed in version 1.9.3 and later.
Affected products
- Uppy companion prior to 1.9.3
Identifiers
- CVE-2020-8135
- GHSA-mm7r-265w-jv6f
Timeline
- 2020-09-03: disclosed: Advisory published
- 2020: patched: Fix released in version 1.9.3