CVE-2016-1693
Published Jun 5, 2016 · Updated Oct 23, 2026
Original summary
Normalized public record · Updated Oct 23, 2026
browser/safe_browsing/srt_field_trial_win.cc in Google Chrome before 51.0.2704.63 does not use the HTTPS service on dl.google.com to obtain the Software Removal Tool, which allows remote attackers to spoof the chrome_cleanup_tool.exe (aka CCT) file via a man-in-the-middle attack on an HTTP session.
Publisher and source text is retained separately from QFinch interpretation.
QFinch assessment
browser/safe_browsing/srt_field_trial_win.cc in Google Chrome before 51.0.2704.63 does not use the HTTPS service on dl.google.com to obtain the Software Removal Tool, which allows remote attackers to spoof the chrome_cleanup_tool.exe (aka CCT) file via a man-in-the-middle attack on an HTTP session.
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
- 90876 ↗
- openSUSE-SU-2016:1496 ↗
- 1035981 ↗
- DSA-3590 ↗
- googlechromereleases.blogspot.com ↗
- openSUSE-SU-2016:1430 ↗
- crbug.com ↗
- RHSA-2016:1190 ↗
- codereview.chromium.org ↗
- GLSA-201607-07 ↗
- openSUSE-SU-2016:1433 ↗
Record history
Published Jun 5, 2016 · Last refreshed Oct 23, 2026