CVE-2016-1687
UnknownEPSS 1.44%
Last modified
CVE-2016-1687 is a vulnerability of currently unknown severity. 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.. EPSS estimates a 1.44% chance of exploitation in the next 30 days.
Description
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.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Debian | Debian Linux | 8.0 |
| Opensuse | Leap | 42.1 |
| Opensuse | Opensuse | 13.2 |
| Redhat | Enterprise Linux Desktop | 6.0 |
| Redhat | Enterprise Linux Server | 6.0 |
| Redhat | Enterprise Linux Workstation | 6.0 |
| Suse | Linux Enterprise | 12.0 |
| Chrome | <= 50.0.2661.102 |
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-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 sensitive information via vectors related to extensions.
How severe is CVE-2016-1687?
Severity scoring for CVE-2016-1687 is pending analysis. The EPSS model estimates a 1.44% probability of exploitation in the next 30 days.
How do I fix CVE-2016-1687?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2016
- CVE-2016-1681Heap-based buffer overflow in the opj_j2k_read_SPCod_SPCoc f…
- CVE-2016-1682The ServiceWorkerContainer::registerServiceWorkerImpl functi…
- CVE-2016-1683numbers.c in libxslt before 1.1.29, as used in Google Chrome…
- CVE-2016-1684numbers.c in libxslt before 1.1.29, as used in Google Chrome…
- CVE-2016-1685core/fxge/ge/fx_ge_text.cpp in PDFium, as used in Google Chr…
- CVE-2016-1686The CPDF_DIBSource::CreateDecoder function in core/fpdfapi/f…
- CVE-2016-1688The regexp (aka regular expression) implementation in Google…
- CVE-2016-1689Heap-based buffer overflow in content/renderer/media/canvas_…
- CVE-2016-1690The Autofill implementation in Google Chrome before 51.0.270…
- CVE-2016-1691Skia, as used in Google Chrome before 51.0.2704.63, mishandl…
- CVE-2016-1692WebKit/Source/core/css/StyleSheetContents.cpp in Blink, as u…
- CVE-2016-1693browser/safe_browsing/srt_field_trial_win.cc in Google Chrom…
Are you affected by CVE-2016-1687?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST