CVE-2016-1630
Published Mar 6, 2016 · Updated Oct 23, 2026
Original summary
Normalized public record · Updated Oct 23, 2026
The ContainerNode::parserRemoveChild function in WebKit/Source/core/dom/ContainerNode.cpp in Blink, as used in Google Chrome before 49.0.2623.75, mishandles widget updates, which makes it easier for remote attackers to bypass the Same Origin Policy via a crafted web site.
Publisher and source text is retained separately from QFinch interpretation.
QFinch assessment
The ContainerNode::parserRemoveChild function in WebKit/Source/core/dom/ContainerNode.cpp in Blink, as used in Google Chrome before 49.0.2623.75, mishandles widget updates, which makes it easier for remote attackers to bypass the Same Origin Policy via a crafted web site.
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
- MEDIUM
- Confidence
- 10%
- Aliases
- None reported
Scores appear only when corresponding evidence exists. Missing data is never interpreted as zero risk.
Sources and record history
- openSUSE-SU-2016:0664 ↗
- openSUSE-SU-2016:0684 ↗
- 84008 ↗
- DSA-3507 ↗
- 1035185 ↗
- openSUSE-SU-2016:0729 ↗
- SUSE-SU-2016:0665 ↗
- GLSA-201603-09 ↗
- codereview.chromium.org ↗
- code.google.com ↗
- USN-2920-1 ↗
- googlechromereleases.blogspot.com ↗
Record history
Published Mar 6, 2016 · Last refreshed Oct 23, 2026