https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 02 Oct 2026 19:41:38 +0000 https://cve.radiocsirt.org/vuln/bdu:2016-02051 bdu:2016-02051 https://cve.radiocsirt.org/vuln/bdu:2016-02051 https://cve.radiocsirt.org/vuln/certfr-2016-avi-247 certfr-2016-avi-247 https://cve.radiocsirt.org/vuln/certfr-2016-avi-247 https://cve.radiocsirt.org/vuln/cnvd-2016-05480 cnvd-2016-05480 https://cve.radiocsirt.org/vuln/cnvd-2016-05480 https://cve.radiocsirt.org/vuln/euvd-2026-82434 EUVD-2026-82434 https://cve.radiocsirt.org/vuln/euvd-2026-82434 https://cve.radiocsirt.org/vuln/fkie_cve-2016-1706 <p>The PPAPI implementation in Google Chrome before 52.0.2743.82 does not validate the origin of IPC messages to the plugin broker process that should have come from the browser process, which allows remote attackers to bypass a sandbox protection mechanism via an unexpected message type, related to broker_process_dispatcher.cc, ppapi_plugin_process_host.cc, ppapi_thread.cc, and render_frame_message_filter.cc.</p> <p>The PPAPI implementation in Google Chrome before 52.0.2743.82 does not validate the origin of IPC messages to the plugin broker process that should have come from the browser process, which allows remote attackers to bypass a sandbox protection mechanism via an unexpected message type, related to broker_process_dispatcher.cc, ppapi_plugin_process_host.cc, ppapi_thread.cc, and render_frame_message_filter.cc.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2016-1706 https://cve.radiocsirt.org/vuln/ghsa-4c3c-m7vg-64hg <p>The PPAPI implementation in Google Chrome before 52.0.2743.82 does not validate the origin of IPC messages to the plugin broker process that should have come from the browser process, which allows remote attackers to bypass a sandbox protection mechanism via an unexpected message type, related to broker_process_dispatcher.cc, ppapi_plugin_process_host.cc, ppapi_thread.cc, and render_frame_message_filter.cc.</p> <p>The PPAPI implementation in Google Chrome before 52.0.2743.82 does not validate the origin of IPC messages to the plugin broker process that should have come from the browser process, which allows remote attackers to bypass a sandbox protection mechanism via an unexpected message type, related to broker_process_dispatcher.cc, ppapi_plugin_process_host.cc, ppapi_thread.cc, and render_frame_message_filter.cc.</p> https://cve.radiocsirt.org/vuln/ghsa-4c3c-m7vg-64hg https://cve.radiocsirt.org/vuln/gsd-2016-1706 gsd-2016-1706 https://cve.radiocsirt.org/vuln/gsd-2016-1706 https://cve.radiocsirt.org/vuln/opensuse-su-2016:1868-1 <p>Security update for Chromium</p> <p>Security update for Chromium</p> https://cve.radiocsirt.org/vuln/opensuse-su-2016:1868-1 https://cve.radiocsirt.org/vuln/rhsa-2016:1485 <p>chromium-browser: various fixes from internal audits chromium-browser: sandbox escape in ppapi chromium-browser: use-after-free in extensions chromium-browser: heap-buffer-overflow in sfntly chromium-browser: same-origin bypass in blink chromium-browser: same-origin bypass in blink chromium-browser: use-after-free in blink chromium-browser: same-origin bypass in v8 chromium-browser: memory corruption in v8 chromium-browser: url spoofing libxml2: Use after free triggered by XPointer paths beginning with range-to chromium-browser: limited same-origin bypass in service workers chromium-browser: origin confusion in proxy authentication chromium-browser: url leakage via pac script chromium-browser: content-security-policy bypass chromium-browser: use after free in extensions chromium-browser: history sniffing with hsts and csp</p> <p>chromium-browser: various fixes from internal audits chromium-browser: sandbox escape in ppapi chromium-browser: use-after-free in extensions chromium-browser: heap-buffer-overflow in sfntly chromium-browser: same-origin bypass in blink chromium-browser: same-origin bypass in blink chromium-browser: use-after-free in blink chromium-browser: same-origin bypass in v8 chromium-browser: memory corruption in v8 chromium-browser: url spoofing libxml2: Use after free triggered by XPointer paths beginning with range-to chromium-browser: limited same-origin bypass in service workers chromium-browser: origin confusion in proxy authentication chromium-browser: url leakage via pac script chromium-browser: content-security-policy bypass chromium-browser: use after free in extensions chromium-browser: history sniffing with hsts and csp</p> https://cve.radiocsirt.org/vuln/rhsa-2016:1485 https://cve.radiocsirt.org/vuln/ubuntu-cve-2016-1706 <p><strong>Affected:</strong> Ubuntu:14.04:LTS: chromium-browser, Ubuntu:14.04:LTS: oxide-qt, Ubuntu:16.04:LTS: chromium-browser, Ubuntu:16.04:LTS: oxide-qt</p> <p>The PPAPI implementation in Google Chrome before 52.0.2743.82 does not validate the origin of IPC messages to the plugin broker process that should have come from the browser process, which allows remote attackers to bypass a sandbox protection mechanism via an unexpected message type, related to broker_process_dispatcher.cc, ppapi_plugin_process_host.cc, ppapi_thread.cc, and render_frame_message_filter.cc.</p> <p><strong>Affected:</strong> Ubuntu:14.04:LTS: chromium-browser, Ubuntu:14.04:LTS: oxide-qt, Ubuntu:16.04:LTS: chromium-browser, Ubuntu:16.04:LTS: oxide-qt</p> <p>The PPAPI implementation in Google Chrome before 52.0.2743.82 does not validate the origin of IPC messages to the plugin broker process that should have come from the browser process, which allows remote attackers to bypass a sandbox protection mechanism via an unexpected message type, related to broker_process_dispatcher.cc, ppapi_plugin_process_host.cc, ppapi_thread.cc, and render_frame_message_filter.cc.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2016-1706