CVE-2017-5011
Published Feb 17, 2017 · Updated Nov 3, 2026
Original summary
Normalized public record · Updated Nov 3, 2026
Google Chrome prior to 56.0.2924.76 for Windows insufficiently sanitized DevTools URLs, which allowed a remote attacker who convinced a user to install a malicious extension to read filesystem contents via a crafted HTML page.
Publisher and source text is retained separately from QFinch interpretation.
QFinch assessment
Google Chrome prior to 56.0.2924.76 for Windows insufficiently sanitized DevTools URLs, which allowed a remote attacker who convinced a user to install a malicious extension to read filesystem contents via a crafted HTML page.
Evidence: public source recordsAffected products
| Affected package, product or range | Fix status |
|---|---|
| Consult the referenced vendor advisory for affected versions. | Consult source advisory |
Matching a version is only one part of assessing exposure. QFinch has not assessed your environment on this public page.
Remediation
Apply the vendor-supported fixed release or mitigation, then verify the affected component is no longer reachable.
- Confirm the affected product and reachable code path exist in your environment.
- Apply the vendor-supported patch or mitigation from the primary advisory.
- Rescan the exact deployed revision and retain verification evidence.
Evidence coverage
- SSVC priority
- LOW
- Confidence
- Not available
- Aliases
- None reported
Scores appear only when corresponding evidence exists. Missing data is never interpreted as zero risk.
Sources and record history
- 95792 ↗
- chromereleases.googleblog.com ↗
- GLSA-201701-66 ↗
- RHSA-2017:0206 ↗
- crbug.com ↗
- 1037718 ↗
- DSA-3776 ↗
Record history
Published Feb 17, 2017 · Last refreshed Nov 3, 2026