Is CVE-2017-18354 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2017-18354 being exploited in the wild.

How severe is CVE-2017-18354?

Low severity, with a CVSS score of 3, published 4 January 2019.

Which products and versions are affected?

rendertron (npm) SEMVER:introduced=0,fixed=1.1.0.

Is there a fix for CVE-2017-18354?

Yes. rendertron (npm): upgrade to 1.1.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2017-18354 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2017-18354?

Check whether you run rendertron (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.

CVE-2017-18354: Google Rendertron local file inclusion vulnerability

CVE-2017-18354 · Severity: low · CVSS 3 · Published 2019-01-04

Rendertron is a service that renders web pages to static HTML, commonly used by search engines and other tools for indexing. A vulnerability in version 1.0.0 allows remote attackers to read arbitrary files from the server by exploiting improper URL validation, enabling unauthorized access to sensitive files without any authentication.

Technologies: rendertron (npm). Vendors: npm.

Quick answers

Is CVE-2017-18354 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2017-18354 being exploited in the wild.
How severe is CVE-2017-18354?: Low severity, with a CVSS score of 3, published 4 January 2019.
Which products and versions are affected?: rendertron (npm) SEMVER:introduced=0,fixed=1.1.0.
Is there a fix for CVE-2017-18354?: Yes. rendertron (npm): upgrade to 1.1.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2017-18354 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2017-18354?: Check whether you run rendertron (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

rendertron (npm): upgrade to 1.1.0 or later
```
npm install rendertron@1.1.0
```

Technical details

Rendertron 1.0.0 is vulnerable to local file inclusion (CWE-22) due to insufficient URL validation. The service accepts alternative protocols (such as 'file://') in addition to HTTP/HTTPS, allowing attackers to craft requests that access the local filesystem. The vulnerability requires only network access and no authentication or user interaction. An attacker can read arbitrary files on the affected server by specifying file:// URLs. The issue was fixed in version 1.1.0 by adding strict URL validation to only permit 'http' and 'https' protocols.

Affected products

Google Rendertron 1.0.0

Identifiers

CVE-2017-18354
GHSA-j87c-cj65-vmh5

Timeline

2019-01-04: disclosed
1.1.0: patched

References

https://github.com/GoogleChrome/rendertron/pull/88

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.