CVE-2016-1705

Multiple unspecified vulnerabilities in chromium before 52.0.2743.82 allow attackers to cause a denial of service or possibly have other impact via unknown vectors. (CVE-2016-1705)

The PPAPI implementation in Chromium 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. (CVE-2016-1706)

The Chrome Web Store inline-installation implementation in the Extensions subsystem in Chromium before 52.0.2743.82 does not properly consider object lifetimes during progress observation, which allows remote attackers to cause a denial of service (use-after-free) or possibly have unspecified other impact via a crafted web site. (CVE-2016-1708)

Heap-based buffer overflow in the ByteArray::Get method in data/byte_array.cc in sfntly before 2016-06-10, as used in Chromium before 52.0.2743.82, allows remote attackers to cause a denial of service or possibly have unspecified other impact via a crafted SFNT font. (CVE-2016-1709)

The ChromeClientImpl::createWindow method in WebKit/Source/web/ChromeClientImpl.cpp in Blink, as used in Chromium before 52.0.2743.82, does not prevent window creation by a deferred frame, which allows remote attackers to bypass the Same Origin Policy via a crafted web site. (CVE-2016-1710)

WebKit/Source/core/loader/FrameLoader.cpp in Blink, as used in Chromium before 52.0.2743.82, does not disable frame navigation during a detach operation on a DocumentLoader object, which allows remote attackers to bypass the Same Origin Policy via a crafted web site. (CVE-2016-1711)

Use-after-free vulnerability in WebKit/Source/core/editing/VisibleUnits.cpp in Blink, as used in Chromium before 52.0.2743.82, allows remote attackers to cause a denial of service or possibly have unspecified other impact via crafted JavaScript code involving an @import at-rule in a Cascading Style Sheets (CSS) token sequence in conjunction with a rel=import attribute of a LINK element. (CVE-2016-5127)

objects.cc in V8 before 5.2.361.27, as used in Chromium before 52.0.2743.82, does not prevent API interceptors from modifying a store target without setting a property, which allows remote attackers to bypass the Same Origin Policy via a crafted web site. (CVE-2016-5128)

V8 before 5.2.361.32, as used in Chromium before 52.0.2743.82, does not properly process left-trimmed objects, which allows remote attackers to cause a denial of service (memory corruption) or possibly have unspecified other impact via crafted JavaScript code. (CVE-2016-5129)

content/renderer/history_controller.cc in Chromium before 52.0.2743.82 does not properly restrict multiple uses of a JavaScript forward method, which allows remote attackers to spoof the URL display via a crafted web site. (CVE-2016-5130)

The Service Workers subsystem in Chromium before 52.0.2743.82 does not properly implement the Secure Contexts specification during decisions about whether to control a subframe, which allows remote attackers to bypass the Same Origin Policy via an https IFRAME element inside an http IFRAME element. (CVE-2016-5132)

Chromium before 52.0.2743.82 mishandles origin information during proxy authentication, which allows man-in-the-middle attackers to spoof a proxy-authentication login prompt or trigger incorrect credential storage by modifying the client-server data stream. (CVE-2016-5133)

net/proxy/proxy_service.cc in the Proxy Auto-Config (PAC) feature in Chromium before 52.0.2743.82 does not ensure that URL information is restricted to a scheme, host, and port, which allows remote attackers to discover credentials by operating a server with a PAC script, a related issue to CVE-2016-3763. (CVE-2016-5134)

WebKit/Source/core/html/parser/HTMLPreloadScanner.cpp in Blink, as…

Chromium was updated to 52.0.2743.82 to fix the following security issues (boo#989901):

• CVE-2016-1706: Sandbox escape in PPAPI
• CVE-2016-1707: URL spoofing on iOS
• CVE-2016-1708: Use-after-free in Extensions
• CVE-2016-1709: Heap-buffer-overflow in sfntly
• CVE-2016-1710: Same-origin bypass in Blink
• CVE-2016-1711: Same-origin bypass in Blink
• CVE-2016-5127: Use-after-free in Blink
• CVE-2016-5128: Same-origin bypass in V8
• CVE-2016-5129: Memory corruption in V8
• CVE-2016-5130: URL spoofing
• CVE-2016-5131: Use-after-free in libxml
• CVE-2016-5132: Limited same-origin bypass in Service Workers
• CVE-2016-5133: Origin confusion in proxy authentication
• CVE-2016-5134: URL leakage via PAC script
• CVE-2016-5135: Content-Security-Policy bypass
• CVE-2016-5136: Use after free in extensions
• CVE-2016-5137: History sniffing with HSTS and CSP
• CVE-2016-1705: Various fixes from internal audits, fuzzing and other initiatives

Chromium was updated to 52.0.2743.82 to fix the following security issues (boo#989901):

• CVE-2016-1706: Sandbox escape in PPAPI
• CVE-2016-1707: URL spoofing on iOS
• CVE-2016-1708: Use-after-free in Extensions
• CVE-2016-1709: Heap-buffer-overflow in sfntly
• CVE-2016-1710: Same-origin bypass in Blink
• CVE-2016-1711: Same-origin bypass in Blink
• CVE-2016-5127: Use-after-free in Blink
• CVE-2016-5128: Same-origin bypass in V8
• CVE-2016-5129: Memory corruption in V8
• CVE-2016-5130: URL spoofing
• CVE-2016-5131: Use-after-free in libxml
• CVE-2016-5132: Limited same-origin bypass in Service Workers
• CVE-2016-5133: Origin confusion in proxy authentication
• CVE-2016-5134: URL leakage via PAC script
• CVE-2016-5135: Content-Security-Policy bypass
• CVE-2016-5136: Use after free in extensions
• CVE-2016-5137: History sniffing with HSTS and CSP
• CVE-2016-1705: Various fixes from internal audits, fuzzing and other initiatives

These are all security issues fixed in the chromedriver-55.0.2883.75-3.1 package on the GA media of openSUSE Tumbleweed.

These are all security issues fixed in the ungoogled-chromium-113.0.5672.92-1.1 package on the GA media of openSUSE Tumbleweed.

Multiple security issues were discovered in Chromium. If a user were tricked in to opening a specially crafted website, an attacker could potentially exploit these to read uninitialized memory, cause a denial of service (application crash) or execute arbitrary code. (CVE-2016-1705)

It was discovered that the PPAPI implementation does not validate the origin of IPC messages to the plugin broker process. A remote attacker could potentially exploit this to bypass sandbox protection mechanisms. (CVE-2016-1706)

It was discovered that Blink does not prevent window creation by a deferred frame. A remote attacker could potentially exploit this to bypass same origin restrictions. (CVE-2016-1710)

It was discovered that Blink does not disable frame navigation during a detach operation on a DocumentLoader object. A remote attacker could potentially exploit this to bypass same origin restrictions. (CVE-2016-1711)

A use-after-free was discovered in Blink. If a user were tricked in to opening a specially crafted website, an attacker could potentially exploit this to cause a denial of service via renderer process crash, or execute arbitrary code. (CVE-2016-5127)

It was discovered that objects.cc in V8 does not prevent API interceptors from modifying a store target without setting a property. A remote attacker could potentially exploit this to bypass same origin restrictions. (CVE-2016-5128)

A memory corruption was discovered in V8. If a user were tricked in to opening a specially crafted website, an attacker could potentially exploit this to cause a denial of service via renderer process crash, or execute arbitrary code. (CVE-2016-5129)

A security issue was discovered in Chromium. A remote attacker could potentially exploit this to spoof the currently displayed URL. (CVE-2016-5130)

A use-after-free was discovered in libxml. If a user were tricked in to opening a specially crafted website, an attacker could potentially exploit this to cause a denial of service via renderer process crash, or execute arbitrary code. (CVE-2016-5131)

The Service Workers implementation in Chromium does not properly implement the Secure Contexts specification during decisions about whether to control a subframe. A remote attacker could potentially exploit this to bypass same origin restrictions. (CVE-2016-5132)

It was discovered that Chromium mishandles origin information during proxy authentication. A machine-in-the-middle attacker could potentially exploit this to spoof a proxy authentication login prompt. (CVE-2016-5133)

It was discovered that the Proxy Auto-Config (PAC) feature in Chromium does not ensure that URL information is restricted to a scheme, host and port. A remote attacker could potentially exploit this to obtain sensitive information. (CVE-2016-5134)

It was discovered that Blink does not consider referrer-policy information inside an HTML document during a preload request. A remote attacker could potentially exploit this to bypass Content Security Policy (CSP) protections. (CVE-2016-5135)

It was discovered that the Content Security Policy (CSP) implementation in Blink does not apply http :80 policies to https :443 URLs. A remote attacker could potentially exploit this to determine whether a specific HSTS web site has been visited by reading a CSP report. (CVE-2016-5137)