CVE-2016-1615
published 2016-01-25CVE-2016-1615: The Omnibox implementation in Google Chrome before 48.0.2564.82 allows remote attackers to spoof a document's origin via unspecified vectors.
PriorityP430medium6.5CVSS 3.0
AVNACLPRNUIRSUCNIHAN
EPSS
1.66%
74.4th percentile
The Omnibox implementation in Google Chrome before 48.0.2564.82 allows remote attackers to spoof a document's origin via unspecified vectors.
Affected
1 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| chrome | <= 47.0.2526.106 | — |
CVSS provenance
nvdv3.06.5MEDIUMCVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
nvdv2.04.3MEDIUMAV:N/AC:M/Au:N/C:N/I:P/A:N
osv6.5MEDIUM
vendor_redhat6.5MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
GHSA
GHSA-xcg2-7p7v-g9cj: The Omnibox implementation in Google Chrome before 48
ghsa_unreviewed·2022-05-17
CVE-2016-1615 [MEDIUM] GHSA-xcg2-7p7v-g9cj: The Omnibox implementation in Google Chrome before 48
The Omnibox implementation in Google Chrome before 48.0.2564.82 allows remote attackers to spoof a document's origin via unspecified vectors.
OSV
CVE-2016-1615: The Omnibox implementation in Google Chrome before 48
osv·2016-01-25·CVSS 6.5
CVE-2016-1615 [MEDIUM] CVE-2016-1615: The Omnibox implementation in Google Chrome before 48
The Omnibox implementation in Google Chrome before 48.0.2564.82 allows remote attackers to spoof a document's origin via unspecified vectors.
Red Hat
chromium-browser: origin confusion in Omnibox
vendor_redhat·2016-01-20·CVSS 6.5
CVE-2016-1615 [MEDIUM] chromium-browser: origin confusion in Omnibox
chromium-browser: origin confusion in Omnibox
The Omnibox implementation in Google Chrome before 48.0.2564.82 allows remote attackers to spoof a document's origin via unspecified vectors.
No detection rules found.
No public exploits indexed.
http://googlechromereleases.blogspot.com/2016/01/stable-channel-update_20.htmlhttp://lists.opensuse.org/opensuse-security-announce/2016-01/msg00035.htmlhttp://lists.opensuse.org/opensuse-security-announce/2016-01/msg00036.htmlhttp://lists.opensuse.org/opensuse-security-announce/2016-01/msg00046.htmlhttp://rhn.redhat.com/errata/RHSA-2016-0072.htmlhttp://www.debian.org/security/2016/dsa-3456http://www.securityfocus.com/bid/81430http://www.securitytracker.com/id/1034801https://code.google.com/p/chromium/issues/detail?id=468179https://security.gentoo.org/glsa/201603-09http://googlechromereleases.blogspot.com/2016/01/stable-channel-update_20.htmlhttp://lists.opensuse.org/opensuse-security-announce/2016-01/msg00035.htmlhttp://lists.opensuse.org/opensuse-security-announce/2016-01/msg00036.htmlhttp://lists.opensuse.org/opensuse-security-announce/2016-01/msg00046.htmlhttp://rhn.redhat.com/errata/RHSA-2016-0072.htmlhttp://www.debian.org/security/2016/dsa-3456http://www.securityfocus.com/bid/81430http://www.securitytracker.com/id/1034801https://code.google.com/p/chromium/issues/detail?id=468179https://security.gentoo.org/glsa/201603-09
2016-01-25
Published