Security context

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

googlechrome/lighthouse

              main @ bb72289
            

Fixes

CVEs

CRITICAL

Peak severity

33.3%

Coverage

Highlights

Code Injection: 1 prior fix. Scrutinize any change in this area.

core/gather/driver/wait-for-condition.js: most-fixed (1 issue). Treat as high-risk during review.

1 high-severity fix in this history; regressions here are high-impact.

Recurring patterns

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

Reflected XSS: The report generator previously suffered from DOM-injection vulnerabilities due to serial string replacement of placeholders like %%LIGHTHOUSE_JSON%% and %%LIGHTHOUSE_JAVASCRIPT%%, allowing unescaped user data to execute code in the context of the generated report.

Sandbox Bypass: Execution of driver logic on target pages using executionContext.evaluate was previously vulnerable to page-level overrides, allowing hostile target page scripts to manipulate internal Lighthouse execution flow.

Code Injection: Dynamic parsing of external utility scripts via eval created risks of local and remote code injection when evaluating source strings instead of using static imports.