CVE-2016-1658
chromium-browser: potential leak of sensitive information to malicious extensions
Overview
Description
The Extensions subsystem in Google Chrome before 50.0.2661.75 incorrectly relies on GetOrigin method calls for origin comparisons, which allows remote attackers to bypass the Same Origin Policy and obtain sensitive information via a crafted extension.
Source: OX vulnerability database
Severity
4.3 · MEDIUM
CVSS 3.0 base score, scored by NVD.
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N
Weakness: CWE-200, CWE-284
Affected packages · 0
No registry package. This ID affects operating system packages only.
Operating systems · 2 fixes
openSUSE 1 release · 2 packages
| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| Tumbleweed | ungoogled-chromium +1 | 113.0.5672.92-1.1 | openSUSE-SU-2024:12948-1 |
| Tumbleweed | chromedriver +1 | 55.0.2883.75-3.1 | openSUSE-SU-2024:10171-1 |
References
- googlechromereleases.blogspot.com http://googlechromereleases.blogspot.com/2016/04/stable-channel-update_13.html
- lists.opensuse.org http://lists.opensuse.org/opensuse-security-announce/2016-04/msg00040.html
- lists.opensuse.org http://lists.opensuse.org/opensuse-security-announce/2016-04/msg00041.html
- lists.opensuse.org http://lists.opensuse.org/opensuse-security-announce/2016-04/msg00049.html
- lists.opensuse.org http://lists.opensuse.org/opensuse-security-announce/2016-04/msg00050.html
- rhn.redhat.com http://rhn.redhat.com/errata/RHSA-2016-0638.html
- www.debian.org http://www.debian.org/security/2016/dsa-3549
- access.redhat.com https://access.redhat.com/security/cve/CVE-2016-1658
- codereview.chromium.org https://codereview.chromium.org/1658913002
- crbug.com https://crbug.com/573317
OX Radar and Response Center
Find threats in your stack.
OX Radar can check high-priority threats, like critical package CVEs, against your context.
Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.