CVE-2016-1687
published 2016-06-05CVE-2016-1687: The renderer implementation in Google Chrome before 51.0.2704.63 does not properly restrict public exposure of classes, which allows remote attackers to obtain…
PriorityP430medium6.5CVSS 3.0
AVNACLPRNUIRSUCHINAN
EPSS
1.44%
73.1th percentile
The renderer implementation in Google Chrome before 51.0.2704.63 does not properly restrict public exposure of classes, which allows remote attackers to obtain sensitive information via vectors related to extensions.
Affected
8 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | debian_linux | — | — |
| chrome | <= 50.0.2661.102 | — | |
| opensuse | leap | — | — |
| opensuse | opensuse | — | — |
| redhat | enterprise_linux_desktop | — | — |
| redhat | enterprise_linux_server | — | — |
| redhat | enterprise_linux_workstation | — | — |
| suse | linux_enterprise | — | — |
CVSS provenance
nvdv3.06.5MEDIUMCVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
nvdv2.04.3MEDIUMAV:N/AC:M/Au:N/C:P/I:N/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-89h7-p99q-pwx5: The renderer implementation in Google Chrome before 51
ghsa_unreviewed·2022-05-14
CVE-2016-1687 [MEDIUM] CWE-200 GHSA-89h7-p99q-pwx5: The renderer implementation in Google Chrome before 51
The renderer implementation in Google Chrome before 51.0.2704.63 does not properly restrict public exposure of classes, which allows remote attackers to obtain sensitive information via vectors related to extensions.
OSV
CVE-2016-1687: The renderer implementation in Google Chrome before 51
osv·2016-06-05·CVSS 6.5
CVE-2016-1687 [MEDIUM] CVE-2016-1687: The renderer implementation in Google Chrome before 51
The renderer implementation in Google Chrome before 51.0.2704.63 does not properly restrict public exposure of classes, which allows remote attackers to obtain sensitive information via vectors related to extensions.
Red Hat
chromium-browser: information leak in extensions
vendor_redhat·2016-05-25·CVSS 6.5
CVE-2016-1687 [MEDIUM] chromium-browser: information leak in extensions
chromium-browser: information leak in extensions
The renderer implementation in Google Chrome before 51.0.2704.63 does not properly restrict public exposure of classes, which allows remote attackers to obtain sensitive information via vectors related to extensions.
No detection rules found.
No public exploits indexed.
Bugzilla
CVE-2016-1687 chromium-browser: information leak in extensions
bugzilla·2016-05-26·CVSS 6.5
CVE-2016-1687 [MEDIUM] CVE-2016-1687 chromium-browser: information leak in extensions
CVE-2016-1687 chromium-browser: information leak in extensions
An information leak flaw was found in the extensions component of the Chromium browser.
Upstream bug(s):
https://code.google.com/p/chromium/issues/detail?id=603748
External References:
http://googlechromereleases.blogspot.com/2016/05/stable-channel-update_25.html
Discussion:
This issue has been addressed in the following products:
Red Hat Enterprise Linux 6 Supplementary
Via RHSA-2016:1190 https://access.redhat.com/errata/RHSA-2016:1190
Bugzilla
CVE-2016-2116 jasper: memory leak in jas_iccprof_createfrombuf()
bugzilla·2016-03-03·CVSS 5.7
CVE-2016-2116 [MEDIUM] CVE-2016-2116 jasper: memory leak in jas_iccprof_createfrombuf()
CVE-2016-2116 jasper: memory leak in jas_iccprof_createfrombuf()
Memory leak in jas_iccprof_createfrombuf function in JasPer 1.900.1 and earlier was found, allowing remote attackers to cause a denial of service (memory consumption) via a crafted ICC color profile in a JPEG 2000 image file.
Vulnerable code:
src/libjasper/base/jas_icc.c:
1685 jas_iccprof_t *jas_iccprof_createfrombuf(uchar *buf, int len)
1686 {
1687 jas_stream_t *in;
1688 jas_iccprof_t *prof;
1689 if (!(in = jas_stream_memopen(JAS_CAST(char *, buf), len)))
1690 goto error;
1691 if (!(prof = jas_iccprof_load(in)))
1692 goto error;
1693 jas_stream_close(in);
1694 return prof;
1695 error:
1696 return 0;
1697 }
jas_stream_t allocated by the call to jas_stream_memopen() is leaked if jas_iccprof_load() fails on line 1691.
Prop
http://googlechromereleases.blogspot.com/2016/05/stable-channel-update_25.htmlhttp://lists.opensuse.org/opensuse-security-announce/2016-05/msg00062.htmlhttp://lists.opensuse.org/opensuse-security-announce/2016-05/msg00063.htmlhttp://lists.opensuse.org/opensuse-security-announce/2016-06/msg00005.htmlhttp://www.debian.org/security/2016/dsa-3590http://www.securityfocus.com/bid/90876http://www.securitytracker.com/id/1035981https://access.redhat.com/errata/RHSA-2016:1190https://codereview.chromium.org/1938123002https://codereview.chromium.org/1939833003https://crbug.com/603748https://security.gentoo.org/glsa/201607-07http://googlechromereleases.blogspot.com/2016/05/stable-channel-update_25.htmlhttp://lists.opensuse.org/opensuse-security-announce/2016-05/msg00062.htmlhttp://lists.opensuse.org/opensuse-security-announce/2016-05/msg00063.htmlhttp://lists.opensuse.org/opensuse-security-announce/2016-06/msg00005.htmlhttp://www.debian.org/security/2016/dsa-3590http://www.securityfocus.com/bid/90876http://www.securitytracker.com/id/1035981https://access.redhat.com/errata/RHSA-2016:1190https://codereview.chromium.org/1938123002https://codereview.chromium.org/1939833003https://crbug.com/603748https://security.gentoo.org/glsa/201607-07
2016-06-05
Published