Security context

What an agent needs to avoid regressing past fixes and find the next vuln in this repo.

medium/phantomjs

              master @ af7ba2a
            

Fixes

CVEs

HIGH

Peak severity

Highlights

Insecure Download: 1 prior fix. Scrutinize any change in this area.

install.js: most-fixed (2 issues). Treat as high-risk during review.

0 high-severity fixes in this history; regressions here are high-impact.

Recurring patterns

The bug types that recur here, drawn from past fixes, not open vulnerabilities.

Arbitrary File Read: Attackers can read arbitrary local files by exploiting the page.open() function with crafted HTML inputs. This exposes sensitive files in environments where PhantomJS is used to render untrusted content.

Insecure Download: The installation process historically fetched PhantomJS binaries without validating their MD5 checksums, leaving users susceptible to executing tampered, malicious, or corrupted payloads.

Insecure Transport: The installation script originally failed to propagate npm certificate authority (CA) configuration to the outbound request. This causes SSL/TLS verification failures or exposes environments with custom CAs to potential MitM vectors during binary fetching.