Google Rendertron vulnerabilities

5 CVEs affecting Google Rendertron, 0 known to be exploited (CISA KEV), with EPSS scores. Latest: CVE-2020-8902, published 2021-02-23.

Highest priority

Known exploited (CISA KEV) first, then by EPSS exploit probability.

CVE-2017-18354, published 2018-12-17. High severity, CVSS 7.5. EPSS: 1.2% chance of exploitation in the next 30 days. Rendertron 1.0.0 allows for alternative protocols such as 'file://' introducing a Local File Inclusion (LFI) bug where arbitrary files can be read by a remote attacker.
CVE-2017-18353, published 2018-12-17. High severity, CVSS 7.5. EPSS: 1.2% chance of exploitation in the next 30 days. Rendertron 1.0.0 includes an _ah/stop route to shutdown the Chrome instance responsible for serving render requests to all users. Visiting this route with a GET request allows any unauthorized remote…
CVE-2017-18355, published 2018-12-17. High severity, CVSS 7.5. EPSS: 1.1% chance of exploitation in the next 30 days. Installed packages are exposed by node_modules in Rendertron 1.0.0, allowing remote attackers to read absolute paths on the server by examining the "_where" attribute of package.json files.
CVE-2017-18352, published 2018-12-17. Medium severity, CVSS 6.1. EPSS: 0.6% chance of exploitation in the next 30 days. Error reporting within Rendertron 1.0.0 allows reflected Cross Site Scripting (XSS) from invalid URLs.
CVE-2020-8902, published 2021-02-23. Medium severity, CVSS 4.3. EPSS: 0.3% chance of exploitation in the next 30 days. Rendertron versions prior to 3.0.0 are are susceptible to a Server-Side Request Forgery (SSRF) attack. An attacker can use a specially crafted webpage to force a rendertron headless chrome process to…