CVE-2017-18353 json
rendertron can remotely shut down Chrome instance
published 2018-12-17 7 y ago modified 2026-06-17 4 mo ago also GHSA-4q69-q4q7-x82c , EUVD-2019-0175
- cvss
- 7.5
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.2%
- EPSS 1.2% chance of exploitation in 30 days, percentile 67%
- public exploits
- 0
- none known
Summary
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 attacker to disable the core service of the application.
Patch / fix
- npm rendertron 1.1.0
- github.com/GoogleChrome/rendertron@8d70628 commit
- github.com/GoogleChrome/rendertron#88 pull request
Exploit prediction
1.15% chance of exploitation in the next 30 days, higher than 67% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- bugs.chromium.org https://bugs.chromium.org/p/chromium/issues/detail?id=759111 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 7.5 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:N/I:N/A:P |
| GitHub | 3.0 | 7.5 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | rendertron | <1.1.0 |
1.1.0 |
Classification
- Weakness
-
- CWE-284 Improper Access Control
References
-
github.com
/GoogleChrome/rendertron/commit/8d70628c96ae72eff6eebb451d26fc9ed6b58b0e
web, patch
-
github.com
/GoogleChrome/rendertron/pull/88
web, patch, third-party-advisory
-
bugs.chromium.org
/p/chromium/issues/detail?id=759111
web, exploit, issue-tracking, vendor-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2017-18353
advisory
-
github.com
/GoogleChrome/rendertron
package
-
github.com
/advisories/GHSA-4q69-q4q7-x82c
advisory
Sources
- CVE List CVE-2017-18353
- GitHub Advisory GHSA-4q69-q4q7-x82c
- NVD CVE-2017-18353
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.