CVE-2019-17221
PhantomJS through 2.1.1 has an arbitrary file read vulnerability, as demonstrated by an XMLHttpRequest for a file:// URI.
Does this matter?
High impact if exploited, but EPSS currently rates exploitation as unlikely (3.42%). Schedule it in the normal patch cycle and watch for a rise in EPSS or a public exploit.
Description
PhantomJS through 2.1.1 has an arbitrary file read vulnerability, as demonstrated by an XMLHttpRequest for a file:// URI. The vulnerability exists in the page.open() function of the webpage module, which loads a specified URL and calls a given callback. An attacker can supply a specially crafted HTML file, as user input, that allows reading arbitrary files on the filesystem. For example, if page.render() is the function callback, this generates a PDF or an image of the targeted file. NOTE: this product is no longer developed.
- CVSS 3.1
- 7.5 HIGHCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
- EPSS
- 3.42% probability · 88th percentile
- CISA KEV
- Not listed
- Weakness
- CWE-552
- Affected
- phantomjs/phantomjs
- Source
- cve@mitre.org
References
- https://www.darkmatter.ae/blogs/breaching-the-perimeter-phantomjs-arbitrary-file-read/Exploit, Third Party Advisory
- https://www.darkmatter.ae/blogs/breaching-the-perimeter-phantomjs-arbitrary-file-read/Exploit, Third Party Advisory
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.