CVE-2016-1664: The HistoryController::UpdateForCommit function in content/renderer/history_controller.cc in Google Chrome before 50.0.2661.94 mishandles…
Noroxi assessment
Priority: Monitor (action score 17/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.98% (FIRST EPSS); higher than 62.7% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. A user must open a link or visit a page. No special conditions are required; it is repeatable.
- Fixed version: chromium-browser (Debian:8) 50.0.2661.94-1~deb8u1; chromium-browser (Red Hat:rhel_extras:6) 0:50.0.2661.94-1.el6; chromium-browser-debuginfo (Red Hat:rhel_extras:6) 0:50.0.2661.94-1.el6.
Low priority for now. Upgrade to chromium-browser (Debian:8) 50.0.2661.94-1~deb8u1; chromium-browser (Red Hat:rhel_extras:6) 0:50.0.2661.94-1.el6; chromium-browser-debuginfo (Red Hat:rhel_extras:6) 0:50.0.2661.94-1.el6 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
The HistoryController::UpdateForCommit function in content/renderer/history_controller.cc in Google Chrome before 50.0.2661.94 mishandles the interaction between subframe forward navigations and other forward navigations, which allows remote attackers to spoof the address bar via a crafted web site.
- Published
- May 14, 2016
- Updated
- Jun 16, 2026
- EPSS
- 0.9% · 62th percentile
- CWE
- CWE-254
Report tools
Action score
17
Low priority for now.
- CVSS
- 17 / 40 · 4.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.9%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| chrome | cpe:2.3:a:google:chrome | |
| redhat | enterprise linux desktop supplementary | cpe:2.3:o:redhat:enterprise_linux_desktop_supplementary |
| redhat | enterprise linux server supplementary | cpe:2.3:o:redhat:enterprise_linux_server_supplementary |
| redhat | enterprise linux server supplementary eus | cpe:2.3:o:redhat:enterprise_linux_server_supplementary_eus |
| redhat | enterprise linux workstation supplementary | cpe:2.3:o:redhat:enterprise_linux_workstation_supplementary |
| opensuse | opensuse | cpe:2.3:o:opensuse:opensuse |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- google chromeup to 50.0.2661.87 inclusive
- opensuse opensuse13.1
- redhat enterprise linux desktop supplementary6.0
- redhat enterprise linux server supplementary6.0
- redhat enterprise linux server supplementary eus6.7z
- redhat enterprise linux workstation supplementary6.0
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:8 | chromium-browser | before 50.0.2661.94-1~deb8u1 | 50.0.2661.94-1~deb8u1 |
| Red Hat:rhel_extras:6 | chromium-browser | before 0:50.0.2661.94-1.el6 | 0:50.0.2661.94-1.el6 |
| Red Hat:rhel_extras:6 | chromium-browser-debuginfo | before 0:50.0.2661.94-1.el6 | 0:50.0.2661.94-1.el6 |
Same product
google: all recordsOther highest-scoring records for the same primary product.
- CVE-2023-4863Heap buffer overflow in libwebp in Google Chrome prior to 116.0.5845.187 and libwebp 1.3.2 allowed a remote attacker to perform an out of…KEV95Now
- CVE-2021-21224Type confusion in V8 in Google Chrome prior to 90.0.4430.85 allowed a remote attacker to execute arbitrary code inside a sandbox via a…KEV90Now
- CVE-2018-17463Incorrect side effect annotation in V8 in Google Chrome prior to 70.0.3538.64 allowed a remote attacker to execute arbitrary code inside a…KEV90Now
Published before and after this one in the same product
- ← EarlierCVE-2016-1661May 14, 2016 · Blink, as used in Google Chrome before 50.0.2661.94, does not ensure that frames satisfy a check for the same renderer process in addition…32Monitor
- ← EarlierCVE-2016-1662May 14, 2016 · extensions/renderer/gc_callback.cc in Google Chrome before 50.0.2661.94 does not prevent fallback execution once the Garbage Collection…40Plan
- Later →CVE-2016-1665May 14, 2016 · The JSGenericLowering class in compiler/js-generic-lowering.cc in Google V8, as used in Google Chrome before 50.0.2661.94, mishandles…27Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:chromium-browser | 50.0.2661.94-1~deb8u1 · Debian:8 | Package registry (OSV) |
| red hat:chromium-browser | 0:50.0.2661.94-1.el6 · Red Hat:rhel_extras:6 | Package registry (OSV) |
| red hat:chromium-browser-debuginfo | 0:50.0.2661.94-1.el6 · Red Hat:rhel_extras:6 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- A user must open a link or visit a page.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- low · data or configuration can be modified
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- Low
- Availability impact
- None
Weakness class (CWE)
CWE-254 · 7PK - Security FeaturesCVSS vector
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (10 more)Show less
- lists.opensuse.org/opensuse-security-announce/2016-05/msg00002.html
- lists.opensuse.org/opensuse-security-announce/2016-05/msg00003.html
- lists.opensuse.org/opensuse-security-announce/2016-05/msg00004.html
- lists.opensuse.org/opensuse-security-announce/2016-06/msg00048.html
- rhn.redhat.com/errata/RHSA-2016-0707.html
- www.debian.org/security/2016/dsa-3564
- www.securityfocus.com/bid/89106
- codereview.chromium.org/1848813005/
- crbug.com/597322
- security.gentoo.org/glsa/201605-02
Vendor advisories and official records. Exploit/PoC links are deliberately left out.