Vulnerabilities > CVE-2015-6768 - Permissions, Privileges, and Access Controls vulnerability in Google Chrome

047910
CVSS 0.0 - NONE
Attack vector
UNKNOWN
Attack complexity
UNKNOWN
Privileges required
UNKNOWN
Confidentiality impact
UNKNOWN
Integrity impact
UNKNOWN
Availability impact
UNKNOWN

Summary

The DOM implementation in Google Chrome before 47.0.2526.73 allows remote attackers to bypass the Same Origin Policy via unspecified vectors, a different vulnerability than CVE-2015-6770.

Vulnerable Configurations

Part Description Count
Application
Google
3745

Common Attack Pattern Enumeration and Classification (CAPEC)

  • Accessing, Modifying or Executing Executable Files
    An attack of this type exploits a system's configuration that allows an attacker to either directly access an executable file, for example through shell access; or in a possible worst case allows an attacker to upload a file and then execute it. Web servers, ftp servers, and message oriented middleware systems which have many integration points are particularly vulnerable, because both the programmers and the administrators must be in synch regarding the interfaces and the correct privileges for each interface.
  • Leverage Executable Code in Non-Executable Files
    An attack of this type exploits a system's trust in configuration and resource files, when the executable loads the resource (such as an image file or configuration file) the attacker has modified the file to either execute malicious code directly or manipulate the target process (e.g. application server) to execute based on the malicious configuration parameters. Since systems are increasingly interrelated mashing up resources from local and remote sources the possibility of this attack occurring is high. The attack can be directed at a client system, such as causing buffer overrun through loading seemingly benign image files, as in Microsoft Security Bulletin MS04-028 where specially crafted JPEG files could cause a buffer overrun once loaded into the browser. Another example targets clients reading pdf files. In this case the attacker simply appends javascript to the end of a legitimate url for a pdf (http://www.gnucitizen.org/blog/danger-danger-danger/) http://path/to/pdf/file.pdf#whatever_name_you_want=javascript:your_code_here The client assumes that they are reading a pdf, but the attacker has modified the resource and loaded executable javascript into the client's browser process. The attack can also target server processes. The attacker edits the resource or configuration file, for example a web.xml file used to configure security permissions for a J2EE app server, adding role name "public" grants all users with the public role the ability to use the administration functionality. The server trusts its configuration file to be correct, but when they are manipulated, the attacker gains full control.
  • Blue Boxing
    This type of attack against older telephone switches and trunks has been around for decades. A tone is sent by an adversary to impersonate a supervisor signal which has the effect of rerouting or usurping command of the line. While the US infrastructure proper may not contain widespread vulnerabilities to this type of attack, many companies are connected globally through call centers and business process outsourcing. These international systems may be operated in countries which have not upgraded Telco infrastructure and so are vulnerable to Blue boxing. Blue boxing is a result of failure on the part of the system to enforce strong authorization for administrative functions. While the infrastructure is different than standard current applications like web applications, there are historical lessons to be learned to upgrade the access control for administrative functions.
  • Restful Privilege Elevation
    Rest uses standard HTTP (Get, Put, Delete) style permissions methods, but these are not necessarily correlated generally with back end programs. Strict interpretation of HTTP get methods means that these HTTP Get services should not be used to delete information on the server, but there is no access control mechanism to back up this logic. This means that unless the services are properly ACL'd and the application's service implementation are following these guidelines then an HTTP request can easily execute a delete or update on the server side. The attacker identifies a HTTP Get URL such as http://victimsite/updateOrder, which calls out to a program to update orders on a database or other resource. The URL is not idempotent so the request can be submitted multiple times by the attacker, additionally, the attacker may be able to exploit the URL published as a Get method that actually performs updates (instead of merely retrieving data). This may result in malicious or inadvertent altering of data on the server.
  • Target Programs with Elevated Privileges
    This attack targets programs running with elevated privileges. The attacker would try to leverage a bug in the running program and get arbitrary code to execute with elevated privileges. For instance an attacker would look for programs that write to the system directories or registry keys (such as HKLM, which stores a number of critical Windows environment variables). These programs are typically running with elevated privileges and have usually not been designed with security in mind. Such programs are excellent exploit targets because they yield lots of power when they break. The malicious user try to execute its code at the same level as a privileged system call.

Nessus

  • NASL familyWindows
    NASL idGOOGLE_CHROME_47_0_2526_73.NASL
    descriptionThe version of Google Chrome installed on the remote Windows host is prior to 47.0.2526.73. It is, therefore, affected by multiple vulnerabilities : - An out-of-bounds access error exists in Google V8 that is triggered when loading array elements. An attacker can exploit this to have an unspecified impact. (CVE-2015-6764) - A use-after-free error exists that is triggered when handling updates. An unauthenticated, remote attacker can exploit this to dereference already freed memory, resulting in the execution of arbitrary code. (CVE-2015-6765) - A use-after-free error exists in AppCache that is triggered when handling updates. An unauthenticated, remote attacker can exploit this to dereference already freed memory, resulting in the execution of arbitrary code. (CVE-2015-6766) - A use-after-free error exists in the OnChannelConnected() function. An unauthenticated, remote attacker can exploit this to dereference already freed memory, resulting in the execution of arbitrary code. (CVE-2015-6767) - A same-origin bypass vulnerability exists due to a flaw that is triggered when handling
    last seen2020-06-01
    modified2020-06-02
    plugin id87206
    published2015-12-04
    reporterThis script is Copyright (C) 2015-2019 and is owned by Tenable, Inc. or an Affiliate thereof.
    sourcehttps://www.tenable.com/plugins/nessus/87206
    titleGoogle Chrome < 47.0.2526.73 Multiple Vulnerabilities
  • NASL familyGentoo Local Security Checks
    NASL idGENTOO_GLSA-201603-09.NASL
    descriptionThe remote host is affected by the vulnerability described in GLSA-201603-09 (Chromium: Multiple vulnerabilities) Multiple vulnerabilities have been discovered in the Chromium web browser. Please review the CVE identifiers referenced below for details. Impact : A remote attacker could possibly execute arbitrary code with the privileges of the process, cause a Denial of Service condition, obtain sensitive information, or bypass security restrictions. Workaround : There is no known workaround at this time.
    last seen2020-06-01
    modified2020-06-02
    plugin id89902
    published2016-03-14
    reporterThis script is Copyright (C) 2016-2019 and is owned by Tenable, Inc. or an Affiliate thereof.
    sourcehttps://www.tenable.com/plugins/nessus/89902
    titleGLSA-201603-09 : Chromium: Multiple vulnerabilities
  • NASL familyMacOS X Local Security Checks
    NASL idMACOSX_GOOGLE_CHROME_47_0_2526_73.NASL
    descriptionThe version of Google Chrome installed on the remote Mac OS X host is prior to 47.0.2526.73. It is, therefore, affected by multiple vulnerabilities : - An out-of-bounds access error exists in Google V8 that is triggered when loading array elements. An attacker can exploit this to have an unspecified impact. (CVE-2015-6764) - A use-after-free error exists that is triggered when handling updates. An unauthenticated, remote attacker can exploit this to dereference already freed memory, resulting in the execution of arbitrary code. (CVE-2015-6765) - A use-after-free error exists in AppCache that is triggered when handling updates. An unauthenticated, remote attacker can exploit this to dereference already freed memory, resulting in the execution of arbitrary code. (CVE-2015-6766) - A use-after-free error exists in the OnChannelConnected() function. An unauthenticated, remote attacker can exploit this to dereference already freed memory, resulting in the execution of arbitrary code. (CVE-2015-6767) - A same-origin bypass vulnerability exists due to a flaw that is triggered when handling
    last seen2020-06-01
    modified2020-06-02
    plugin id87207
    published2015-12-04
    reporterThis script is Copyright (C) 2015-2019 and is owned by Tenable, Inc. or an Affiliate thereof.
    sourcehttps://www.tenable.com/plugins/nessus/87207
    titleGoogle Chrome < 47.0.2526.73 Multiple Vulnerabilities (Mac OS X)
  • NASL familyFreeBSD Local Security Checks
    NASL idFREEBSD_PKG_548F74BD993C11E5956B00262D5ED8EE.NASL
    descriptionGoogle Chrome Releases reports : 41 security fixes in this release, including : - [558589] Critical CVE-2015-6765: Use-after-free in AppCache. Credit to anonymous. - [551044] High CVE-2015-6766: Use-after-free in AppCache. Credit to anonymous. - [554908] High CVE-2015-6767: Use-after-free in AppCache. Credit to anonymous. - [556724] High CVE-2015-6768: Cross-origin bypass in DOM. Credit to Mariusz Mlynski. - [534923] High CVE-2015-6769: Cross-origin bypass in core. Credit to Mariusz Mlynski. - [541206] High CVE-2015-6770: Cross-origin bypass in DOM. Credit to Mariusz Mlynski. - [544991] High CVE-2015-6771: Out of bounds access in v8. Credit to anonymous. - [546545] High CVE-2015-6772: Cross-origin bypass in DOM. Credit to Mariusz Mlynski. - [554946] High CVE-2015-6764: Out of bounds access in v8. Credit to Guang Gong of Qihoo 360 via pwn2own. - [491660] High CVE-2015-6773: Out of bounds access in Skia. Credit to cloudfuzzer. - [549251] High CVE-2015-6774: Use-after-free in Extensions. Credit to anonymous. - [529012] High CVE-2015-6775: Type confusion in PDFium. Credit to Atte Kettunen of OUSPG. - [457480] High CVE-2015-6776: Out of bounds access in PDFium. Credit to Hanno Bock. - [544020] High CVE-2015-6777: Use-after-free in DOM. Credit to Long Liu of Qihoo 360Vulcan Team. - [514891] Medium CVE-2015-6778: Out of bounds access in PDFium. Credit to Karl Skomski. - [528505] Medium CVE-2015-6779: Scheme bypass in PDFium. Credit to Til Jasper Ullrich. - [490492] Medium CVE-2015-6780: Use-after-free in Infobars. Credit to Khalil Zhani. - [497302] Medium CVE-2015-6781: Integer overflow in Sfntly. Credit to miaubiz. - [536652] Medium CVE-2015-6782: Content spoofing in Omnibox. Credit to Luan Herrera. - [537205] Medium CVE-2015-6783: Signature validation issue in Android Crazy Linker. Credit to Michal Bednarski. - [503217] Low CVE-2015-6784: Escaping issue in saved pages. Credit to Inti De Ceukelaire. - [534542] Low CVE-2015-6785: Wildcard matching issue in CSP. Credit to Michael Ficarra / Shape Security. - [534570] Low CVE-2015-6786: Scheme bypass in CSP. Credit to Michael Ficarra / Shape Security. - [563930] CVE-2015-6787: Various fixes from internal audits, fuzzing and other initiatives. - Multiple vulnerabilities in V8 fixed at the tip of the 4.7 branch (currently 4.7.80.23).
    last seen2020-06-01
    modified2020-06-02
    plugin id87177
    published2015-12-03
    reporterThis script is Copyright (C) 2015-2019 and is owned by Tenable, Inc. or an Affiliate thereof.
    sourcehttps://www.tenable.com/plugins/nessus/87177
    titleFreeBSD : chromium -- multiple vulnerabilities (548f74bd-993c-11e5-956b-00262d5ed8ee)
  • NASL familyRed Hat Local Security Checks
    NASL idREDHAT-RHSA-2015-2545.NASL
    descriptionUpdated chromium-browser packages that fix multiple security issues are now available for Red Hat Enterprise Linux 6 Supplementary. Red Hat Product Security has rated this update as having Critical security impact. Common Vulnerability Scoring System (CVSS) base scores, which give detailed severity ratings, are available for each vulnerability from the CVE links in the References section. Chromium is an open source web browser, powered by WebKit (Blink). Several flaws were found in the processing of malformed web content. A web page containing malicious content could cause Chromium to crash, execute arbitrary code, or disclose sensitive information when visited by the victim. (CVE-2015-6764, CVE-2015-6765, CVE-2015-6766, CVE-2015-6767, CVE-2015-6768, CVE-2015-6769, CVE-2015-6770, CVE-2015-6771, CVE-2015-6772, CVE-2015-6773, CVE-2015-6774, CVE-2015-6775, CVE-2015-6776, CVE-2015-6777, CVE-2015-6778, CVE-2015-6779, CVE-2015-6780, CVE-2015-6781, CVE-2015-6782, CVE-2015-6784, CVE-2015-6785, CVE-2015-6786, CVE-2015-6787) All Chromium users should upgrade to these updated packages, which contain Chromium version 47.0.2526.73, which corrects these issues. After installing the update, Chromium must be restarted for the changes to take effect.
    last seen2020-05-31
    modified2015-12-04
    plugin id87195
    published2015-12-04
    reporterThis script is Copyright (C) 2015-2020 and is owned by Tenable, Inc. or an Affiliate thereof.
    sourcehttps://www.tenable.com/plugins/nessus/87195
    titleRHEL 6 : chromium-browser (RHSA-2015:2545)
  • NASL familyUbuntu Local Security Checks
    NASL idUBUNTU_USN-2825-1.NASL
    descriptionMultiple use-after-free bugs were discovered in the application cache implementation in Chromium. If a user were tricked in to opening a specially crafted website, an attacker could potentially exploit these to cause a denial of service via application crash, or execute arbitrary code with the privileges of the user invoking the program. (CVE-2015-6765, CVE-2015-6766, CVE-2015-6767) Several security issues were discovered in the DOM implementation in Chromium. If a user were tricked in to opening a specially crafted website, an attacker could potentially exploit these to bypass same origin restrictions. (CVE-2015-6768, CVE-2015-6770) A security issue was discovered in the provisional-load commit implementation in Chromium. If a user were tricked in to opening a specially crafted website, an attacker could potentially exploit this to bypass same origin restrictions. (CVE-2015-6769) An out-of-bounds read was discovered in the array map and filter operations in V8 in some circumstances. 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 crash. (CVE-2015-6771) It was discovered that the DOM implementation in Chromium does not prevent javascript: URL navigation while a document is being detached. If a user were tricked in to opening a specially crafted website, an attacker could potentially exploit this to bypass same origin restrictions. (CVE-2015-6772) An out-of bounds read was discovered in Skia in some cirumstances. 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 crash. (CVE-2015-6773) A use-after-free was discovered in the DOM implementation in Chromium. 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 crash or execute arbitrary code with the privileges of the sandboxed render process. (CVE-2015-6777) It was discovered that the Document::open function in Chromium did not ensure that page-dismissal event handling is compatible with modal dialog blocking. If a user were tricked in to opening a specially crafted website, an attacker could potentially exploit this to spoof application UI content. (CVE-2015-6782) It was discovered that the page serializer in Chromium mishandled MOTW comments for URLs in some circumstances. An attacker could potentially exploit this to inject HTML content. (CVE-2015-6784) It was discovered that the Content Security Policy (CSP) implementation in Chromium accepted an x.y hostname as a match for a *.x.y pattern. An attacker could potentially exploit this to bypass intended access restrictions. (CVE-2015-6785) It was discovered that the Content Security Policy (CSP) implementation in Chromium accepted blob:, data: and filesystem: URLs as a match for a * pattern. An attacker could potentially exploit this to bypass intended access restrictions. (CVE-2015-6786) 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 via application crash or execute arbitrary code with the privileges of the user invoking the program. (CVE-2015-6787) Multiple security issues were discovered in V8. 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 via renderer crash or execute arbitrary code with the privileges of the sandboxed render process. (CVE-2015-8478). Note that Tenable Network Security has extracted the preceding description block directly from the Ubuntu security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.
    last seen2020-06-01
    modified2020-06-02
    plugin id87320
    published2015-12-11
    reporterUbuntu Security Notice (C) 2015-2019 Canonical, Inc. / NASL script (C) 2015-2019 and is owned by Tenable, Inc. or an Affiliate thereof.
    sourcehttps://www.tenable.com/plugins/nessus/87320
    titleUbuntu 14.04 LTS / 15.04 / 15.10 : oxide-qt vulnerabilities (USN-2825-1)
  • NASL familySuSE Local Security Checks
    NASL idOPENSUSE-2015-912.NASL
    descriptionChromium was updated to 47.0.2526.80 to fix security issues and bugs. The following vulnerabilities were fixed : - CVE-2015-6788: Type confusion in extensions - CVE-2015-6789: Use-after-free in Blink - CVE-2015-6790: Escaping issue in saved pages - CVE-2015-6791: Various fixes from internal audits, fuzzing and other initiatives The following vulnerabilities were fixed in 47.0.2526.73 : - CVE-2015-6765: Use-after-free in AppCache - CVE-2015-6766: Use-after-free in AppCache - CVE-2015-6767: Use-after-free in AppCache - CVE-2015-6768: Cross-origin bypass in DOM - CVE-2015-6769: Cross-origin bypass in core - CVE-2015-6770: Cross-origin bypass in DOM - CVE-2015-6771: Out of bounds access in v8 - CVE-2015-6772: Cross-origin bypass in DOM - CVE-2015-6764: Out of bounds access in v8 - CVE-2015-6773: Out of bounds access in Skia - CVE-2015-6774: Use-after-free in Extensions - CVE-2015-6775: Type confusion in PDFium - CVE-2015-6776: Out of bounds access in PDFium - CVE-2015-6777: Use-after-free in DOM - CVE-2015-6778: Out of bounds access in PDFium - CVE-2015-6779: Scheme bypass in PDFium - CVE-2015-6780: Use-after-free in Infobars - CVE-2015-6781: Integer overflow in Sfntly - CVE-2015-6782: Content spoofing in Omnibox - CVE-2015-6783: Signature validation issue in Android Crazy Linker. - CVE-2015-6784: Escaping issue in saved pages - CVE-2015-6785: Wildcard matching issue in CSP - CVE-2015-6786: Scheme bypass in CSP - CVE-2015-6787: Various fixes from internal audits, fuzzing and other initiatives. - Multiple vulnerabilities in V8 fixed at the tip of the 4.7 branch (currently 4.7.80.23)
    last seen2020-06-05
    modified2015-12-18
    plugin id87488
    published2015-12-18
    reporterThis script is Copyright (C) 2015-2020 Tenable Network Security, Inc.
    sourcehttps://www.tenable.com/plugins/nessus/87488
    titleopenSUSE Security Update : Chromium (openSUSE-2015-912)
  • NASL familyDebian Local Security Checks
    NASL idDEBIAN_DSA-3415.NASL
    descriptionSeveral vulnerabilities have been discovered in the chromium web browser. - CVE-2015-1302 Rub Wu discovered an information leak in the pdfium library. - CVE-2015-6764 Guang Gong discovered an out-of-bounds read issue in the v8 JavaScript library. - CVE-2015-6765 A use-after-free issue was discovered in AppCache. - CVE-2015-6766 A use-after-free issue was discovered in AppCache. - CVE-2015-6767 A use-after-free issue was discovered in AppCache. - CVE-2015-6768 Mariusz Mlynski discovered a way to bypass the Same Origin Policy. - CVE-2015-6769 Mariusz Mlynski discovered a way to bypass the Same Origin Policy. - CVE-2015-6770 Mariusz Mlynski discovered a way to bypass the Same Origin Policy. - CVE-2015-6771 An out-of-bounds read issue was discovered in the v8 JavaScript library. - CVE-2015-6772 Mariusz Mlynski discovered a way to bypass the Same Origin Policy. - CVE-2015-6773 cloudfuzzer discovered an out-of-bounds read issue in the skia library. - CVE-2015-6774 A use-after-free issue was found in extensions binding. - CVE-2015-6775 Atte Kettunen discovered a type confusion issue in the pdfium library. - CVE-2015-6776 Hanno Bock dicovered an out-of-bounds access issue in the openjpeg library, which is used by pdfium. - CVE-2015-6777 Long Liu found a use-after-free issue. - CVE-2015-6778 Karl Skomski found an out-of-bounds read issue in the pdfium library. - CVE-2015-6779 Til Jasper Ullrich discovered that the pdfium library does not sanitize
    last seen2020-06-01
    modified2020-06-02
    plugin id87289
    published2015-12-10
    reporterThis script is Copyright (C) 2015-2019 and is owned by Tenable, Inc. or an Affiliate thereof.
    sourcehttps://www.tenable.com/plugins/nessus/87289
    titleDebian DSA-3415-1 : chromium-browser - security update

Redhat

rpms
  • chromium-browser-0:47.0.2526.73-1.el6
  • chromium-browser-debuginfo-0:47.0.2526.73-1.el6

Seebug

bulletinFamilyexploit
description#### VULNERABILITY DETAILS From /third_party/WebKit/Source/core/dom/Document.cpp: `` bool FrameLoader::prepareForCommit() { PluginScriptForbiddenScope forbidPluginDestructorScripting; RefPtrWillBeRawPtr pdl = m_provisionalDocumentLoader; (...) if (m_documentLoader) { client()-&gt;dispatchWillClose(); dispatchUnloadEvent(); } m_frame-&gt;detachChildren(); // The previous calls to dispatchUnloadEvent() and detachChildren() can // execute arbitrary script via things like unload events. If the executed // script intiates a new load or causes the current frame to be detached, // we need to abandon the current load. if (pdl != m_provisionalDocumentLoader) return false; (...) if (m_frame-&gt;document()) m_frame-&gt;document()-&gt;detach(); m_documentLoader = m_provisionalDocumentLoader. release(); m_frame-&gt;updateFrameSecurityOrigin(); return true; } `` This logic depends on the assumption that dispatching the unload event will advance the navigated document's |LoadEventProgress| state to UnloadEventHandled, such that creation of subframes will be suppressed. The frame's document may change through synchronous loads, though. Normally, this is okay because the load will detach the provisional loader from the frame, and the |(pdl != m_provisionalDocumentLoader)| check will catch this. However, if the replacement occurs through loading a javascript: URI during a page dismissal event, which suppresses detaching loaders, the provisional loader will remain attached. As a result, an attacker will be able to attach subframes that will persist in the frame tree of a cross-origin document. #### VERSION Chrome 46.0.2490.86 (Stable) Chrome 47.0.2526.58 (Beta) Chrome 48.0.2560.0 (Dev) Chromium 49.0.2566.0 (Release build compiled today) Attachment: [CVE-2015-6768](<http://paper.seebug.org/papers/Archive/poc/CVE-2015-6768.zip>)
idSSV:93027
last seen2017-11-19
modified2017-04-24
published2017-04-24
reporterRoot
titleChrome Universal XSS via persistence of subframes (CVE-2015-6768)