Vulnerabilities > CVE-2019-5773 - Origin Validation Error vulnerability in multiple products

047910
CVSS 6.5 - MEDIUM
Attack vector
NETWORK
Attack complexity
LOW
Privileges required
NONE
Confidentiality impact
NONE
Integrity impact
HIGH
Availability impact
NONE
network
low complexity
google
debian
redhat
fedoraproject
CWE-346
nessus

Summary

Insufficient origin validation in IndexedDB in Google Chrome prior to 72.0.3626.81 allowed a remote attacker who had compromised the renderer process to bypass same origin policy via a crafted HTML page.

Vulnerable Configurations

Part Description Count
Application
Google
4526
OS
Debian
1
OS
Redhat
3
OS
Fedoraproject
2

Common Weakness Enumeration (CWE)

Common Attack Pattern Enumeration and Classification (CAPEC)

  • JSON Hijacking (aka JavaScript Hijacking)
    An attacker targets a system that uses JavaScript Object Notation (JSON) as a transport mechanism between the client and the server (common in Web 2.0 systems using AJAX) to steal possibly confidential information transmitted from the server back to the client inside the JSON object by taking advantage of the loophole in the browser's Same Origin Policy that does not prohibit JavaScript from one website to be included and executed in the context of another website. An attacker gets the victim to visit his or her malicious page that contains a script tag whose source points to the vulnerable system with a URL that requests a response from the server containing a JSON object with possibly confidential information. The malicious page also contains malicious code to capture the JSON object returned by the server before any other processing on it can take place, typically by overriding the JavaScript function used to create new objects. This hook allows the malicious code to get access to the creation of each object and transmit the possibly sensitive contents of the captured JSON object to the attackers' server. There is nothing in the browser's security model to prevent the attackers' malicious JavaScript code (originating from attacker's domain) to set up an environment (as described above) to intercept a JSON object response (coming from the vulnerable target system's domain), read its contents and transmit to the attackers' controlled site. The same origin policy protects the domain object model (DOM), but not the JSON.
  • Cache Poisoning
    An attacker exploits the functionality of cache technologies to cause specific data to be cached that aids the attackers' objectives. This describes any attack whereby an attacker places incorrect or harmful material in cache. The targeted cache can be an application's cache (e.g. a web browser cache) or a public cache (e.g. a DNS or ARP cache). Until the cache is refreshed, most applications or clients will treat the corrupted cache value as valid. This can lead to a wide range of exploits including redirecting web browsers towards sites that install malware and repeatedly incorrect calculations based on the incorrect value.
  • DNS Cache Poisoning
    A domain name server translates a domain name (such as www.example.com) into an IP address that Internet hosts use to contact Internet resources. An attacker modifies a public DNS cache to cause certain names to resolve to incorrect addresses that the attacker specifies. The result is that client applications that rely upon the targeted cache for domain name resolution will be directed not to the actual address of the specified domain name but to some other address. Attackers can use this to herd clients to sites that install malware on the victim's computer or to masquerade as part of a Pharming attack.
  • Exploitation of Session Variables, Resource IDs and other Trusted Credentials
    Attacks on session IDs and resource IDs take advantage of the fact that some software accepts user input without verifying its authenticity. For example, a message queuing system that allows service requesters to post messages to its queue through an open channel (such as anonymous FTP), authorization is done through checking group or role membership contained in the posted message. However, there is no proof that the message itself, the information in the message (such group or role membership), or indeed the process that wrote the message to the queue are authentic and authorized to do so. Many server side processes are vulnerable to these attacks because the server to server communications have not been analyzed from a security perspective or the processes "trust" other systems because they are behind a firewall. In a similar way servers that use easy to guess or spoofable schemes for representing digital identity can also be vulnerable. Such systems frequently use schemes without cryptography and digital signatures (or with broken cryptography). Session IDs may be guessed due to insufficient randomness, poor protection (passed in the clear), lack of integrity (unsigned), or improperly correlation with access control policy enforcement points. Exposed configuration and properties files that contain system passwords, database connection strings, and such may also give an attacker an edge to identify these identifiers. The net result is that spoofing and impersonation is possible leading to an attacker's ability to break authentication, authorization, and audit controls on the system.
  • Application API Message Manipulation via Man-in-the-Middle
    An attacker manipulates either egress or ingress data from a client within an application framework in order to change the content of messages. Performing this attack can allow the attacker to gain unauthorized privileges within the application, or conduct attacks such as phishing, deceptive strategies to spread malware, or traditional web-application attacks. The techniques require use of specialized software that allow the attacker to man-in-the-middle communications between the web browser and the remote system. Despite the use of MITM software, the attack is actually directed at the server, as the client is one node in a series of content brokers that pass information along to the application framework. Additionally, it is not true "Man-in-the-Middle" attack at the network layer, but an application-layer attack the root cause of which is the master applications trust in the integrity of code supplied by the client.

Nessus

  • NASL familyRed Hat Local Security Checks
    NASL idREDHAT-RHSA-2019-0309.NASL
    descriptionAn update for chromium-browser is now available for Red Hat Enterprise Linux 6 Supplementary. Red Hat Product Security has rated this update as having a security impact of Critical. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available for each vulnerability from the CVE link(s) in the References section. Chromium is an open source web browser, powered by WebKit (Blink). This update upgrades Chromium to version 72.0.3626.81. Security Fix(es) : * chromium-browser: Inappropriate implementation in QUIC Networking (CVE-2019-5754) * chromium-browser: Inappropriate implementation in V8 (CVE-2019-5755) * chromium-browser: Use after free in PDFium (CVE-2019-5756) * chromium-browser: Type Confusion in SVG (CVE-2019-5757) * chromium-browser: Use after free in Blink (CVE-2019-5758) * chromium-browser: Use after free in HTML select elements (CVE-2019-5759) * chromium-browser: Use after free in WebRTC (CVE-2019-5760) * chromium-browser: Use after free in SwiftShader (CVE-2019-5761) * chromium-browser: Use after free in PDFium (CVE-2019-5762) * chromium-browser: Insufficient validation of untrusted input in V8 (CVE-2019-5763) * chromium-browser: Use after free in WebRTC (CVE-2019-5764) * chromium-browser: Insufficient policy enforcement in the browser (CVE-2019-5765) * chromium-browser: Inappropriate implementation in V8 (CVE-2019-5782) * chromium-browser: Insufficient policy enforcement in Canvas (CVE-2019-5766) * chromium-browser: Incorrect security UI in WebAPKs (CVE-2019-5767) * chromium-browser: Insufficient policy enforcement in DevTools (CVE-2019-5768) * chromium-browser: Insufficient validation of untrusted input in Blink (CVE-2019-5769) * chromium-browser: Heap buffer overflow in WebGL (CVE-2019-5770) * chromium-browser: Heap buffer overflow in SwiftShader (CVE-2019-5771) * chromium-browser: Use after free in PDFium (CVE-2019-5772) * chromium-browser: Insufficient data validation in IndexedDB (CVE-2019-5773) * chromium-browser: Insufficient validation of untrusted input in SafeBrowsing (CVE-2019-5774) * chromium-browser: Insufficient policy enforcement in Omnibox (CVE-2019-5775) * chromium-browser: Insufficient policy enforcement in Omnibox (CVE-2019-5776) * chromium-browser: Insufficient policy enforcement in Omnibox (CVE-2019-5777) * chromium-browser: Insufficient policy enforcement in Extensions (CVE-2019-5778) * chromium-browser: Insufficient policy enforcement in ServiceWorker (CVE-2019-5779) * chromium-browser: Insufficient policy enforcement (CVE-2019-5780) * chromium-browser: Insufficient policy enforcement in Omnibox (CVE-2019-5781) For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.
    last seen2020-05-31
    modified2019-02-12
    plugin id122112
    published2019-02-12
    reporterThis script is Copyright (C) 2019-2020 and is owned by Tenable, Inc. or an Affiliate thereof.
    sourcehttps://www.tenable.com/plugins/nessus/122112
    titleRHEL 6 : chromium-browser (RHSA-2019:0309)
  • NASL familyDebian Local Security Checks
    NASL idDEBIAN_DSA-4395.NASL
    descriptionSeveral vulnerabilities have been discovered in the chromium web browser. - CVE-2018-17481 A use-after-free issue was discovered in the pdfium library. - CVE-2019-5754 Klzgrad discovered an error in the QUIC networking implementation. - CVE-2019-5755 Jay Bosamiya discovered an implementation error in the v8 JavaScript library. - CVE-2019-5756 A use-after-free issue was discovered in the pdfium library. - CVE-2019-5757 Alexandru Pitis discovered a type confusion error in the SVG image format implementation. - CVE-2019-5758 Zhe Jin discovered a use-after-free issue in blink/webkit. - CVE-2019-5759 Almog Benin discovered a use-after-free issue when handling HTML pages containing select elements. - CVE-2019-5760 Zhe Jin discovered a use-after-free issue in the WebRTC implementation. - CVE-2019-5762 A use-after-free issue was discovered in the pdfium library. - CVE-2019-5763 Guang Gon discovered an input validation error in the v8 JavaScript library. - CVE-2019-5764 Eyal Itkin discovered a use-after-free issue in the WebRTC implementation. - CVE-2019-5765 Sergey Toshin discovered a policy enforcement error. - CVE-2019-5766 David Erceg discovered a policy enforcement error. - CVE-2019-5767 Haoran Lu, Yifan Zhang, Luyi Xing, and Xiaojing Liao reported an error in the WebAPKs user interface. - CVE-2019-5768 Rob Wu discovered a policy enforcement error in the developer tools. - CVE-2019-5769 Guy Eshel discovered an input validation error in blink/webkit. - CVE-2019-5770 hemidallt discovered a buffer overflow issue in the WebGL implementation. - CVE-2019-5772 Zhen Zhou discovered a use-after-free issue in the pdfium library. - CVE-2019-5773 Yongke Wong discovered an input validation error in the IndexDB implementation. - CVE-2019-5774 Junghwan Kang and Juno Im discovered an input validation error in the SafeBrowsing implementation. - CVE-2019-5775 evil1m0 discovered a policy enforcement error. - CVE-2019-5776 Lnyas Zhang discovered a policy enforcement error. - CVE-2019-5777 Khalil Zhani discovered a policy enforcement error. - CVE-2019-5778 David Erceg discovered a policy enforcement error in the Extensions implementation. - CVE-2019-5779 David Erceg discovered a policy enforcement error in the ServiceWorker implementation. - CVE-2019-5780 Andreas Hegenberg discovered a policy enforcement error. - CVE-2019-5781 evil1m0 discovered a policy enforcement error. - CVE-2019-5782 Qixun Zhao discovered an implementation error in the v8 JavaScript library. - CVE-2019-5783 Shintaro Kobori discovered an input validation error in the developer tools. - CVE-2019-5784 Lucas Pinheiro discovered an implementation error in the v8 JavaScript library.
    last seen2020-06-01
    modified2020-06-02
    plugin id122272
    published2019-02-19
    reporterThis script is Copyright (C) 2019-2020 and is owned by Tenable, Inc. or an Affiliate thereof.
    sourcehttps://www.tenable.com/plugins/nessus/122272
    titleDebian DSA-4395-1 : chromium - security update
  • NASL familySuSE Local Security Checks
    NASL idOPENSUSE-2019-205.NASL
    descriptionThis update for Chromium to version 72.0.3626.96 fixes the following issues : Security issues fixed (bsc#1123641 and bsc#1124936) : - CVE-2019-5784: Inappropriate implementation in V8 - CVE-2019-5754: Inappropriate implementation in QUIC Networking. - CVE-2019-5782: Inappropriate implementation in V8. - CVE-2019-5755: Inappropriate implementation in V8. - CVE-2019-5756: Use after free in PDFium. - CVE-2019-5757: Type Confusion in SVG. - CVE-2019-5758: Use after free in Blink. - CVE-2019-5759: Use after free in HTML select elements. - CVE-2019-5760: Use after free in WebRTC. - CVE-2019-5761: Use after free in SwiftShader. - CVE-2019-5762: Use after free in PDFium. - CVE-2019-5763: Insufficient validation of untrusted input in V8. - CVE-2019-5764: Use after free in WebRTC. - CVE-2019-5765: Insufficient policy enforcement in the browser. - CVE-2019-5766: Insufficient policy enforcement in Canvas. - CVE-2019-5767: Incorrect security UI in WebAPKs. - CVE-2019-5768: Insufficient policy enforcement in DevTools. - CVE-2019-5769: Insufficient validation of untrusted input in Blink. - CVE-2019-5770: Heap buffer overflow in WebGL. - CVE-2019-5771: Heap buffer overflow in SwiftShader. - CVE-2019-5772: Use after free in PDFium. - CVE-2019-5773: Insufficient data validation in IndexedDB. - CVE-2019-5774: Insufficient validation of untrusted input in SafeBrowsing. - CVE-2019-5775: Insufficient policy enforcement in Omnibox. - CVE-2019-5776: Insufficient policy enforcement in Omnibox. - CVE-2019-5777: Insufficient policy enforcement in Omnibox. - CVE-2019-5778: Insufficient policy enforcement in Extensions. - CVE-2019-5779: Insufficient policy enforcement in ServiceWorker. - CVE-2019-5780: Insufficient policy enforcement. - CVE-2019-5781: Insufficient policy enforcement in Omnibox. For a full list of changes refer to https://chromereleases.googleblog.com/2019/02/stable-channel-update-fo r-desktop.html
    last seen2020-06-01
    modified2020-06-02
    plugin id122305
    published2019-02-19
    reporterThis script is Copyright (C) 2019-2020 and is owned by Tenable, Inc. or an Affiliate thereof.
    sourcehttps://www.tenable.com/plugins/nessus/122305
    titleopenSUSE Security Update : chromium (openSUSE-2019-205)
  • NASL familySuSE Local Security Checks
    NASL idOPENSUSE-2019-204.NASL
    descriptionThis update for Chromium to version 72.0.3626.96 fixes the following issues : Security issues fixed (bsc#1123641 and bsc#1124936) : - CVE-2019-5784: Inappropriate implementation in V8 - CVE-2019-5754: Inappropriate implementation in QUIC Networking. - CVE-2019-5782: Inappropriate implementation in V8. - CVE-2019-5755: Inappropriate implementation in V8. - CVE-2019-5756: Use after free in PDFium. - CVE-2019-5757: Type Confusion in SVG. - CVE-2019-5758: Use after free in Blink. - CVE-2019-5759: Use after free in HTML select elements. - CVE-2019-5760: Use after free in WebRTC. - CVE-2019-5761: Use after free in SwiftShader. - CVE-2019-5762: Use after free in PDFium. - CVE-2019-5763: Insufficient validation of untrusted input in V8. - CVE-2019-5764: Use after free in WebRTC. - CVE-2019-5765: Insufficient policy enforcement in the browser. - CVE-2019-5766: Insufficient policy enforcement in Canvas. - CVE-2019-5767: Incorrect security UI in WebAPKs. - CVE-2019-5768: Insufficient policy enforcement in DevTools. - CVE-2019-5769: Insufficient validation of untrusted input in Blink. - CVE-2019-5770: Heap buffer overflow in WebGL. - CVE-2019-5771: Heap buffer overflow in SwiftShader. - CVE-2019-5772: Use after free in PDFium. - CVE-2019-5773: Insufficient data validation in IndexedDB. - CVE-2019-5774: Insufficient validation of untrusted input in SafeBrowsing. - CVE-2019-5775: Insufficient policy enforcement in Omnibox. - CVE-2019-5776: Insufficient policy enforcement in Omnibox. - CVE-2019-5777: Insufficient policy enforcement in Omnibox. - CVE-2019-5778: Insufficient policy enforcement in Extensions. - CVE-2019-5779: Insufficient policy enforcement in ServiceWorker. - CVE-2019-5780: Insufficient policy enforcement. - CVE-2019-5781: Insufficient policy enforcement in Omnibox. For a full list of changes refer to https://chromereleases.googleblog.com/2019/02/stable-channel-update-fo r-desktop.html
    last seen2020-05-31
    modified2019-02-19
    plugin id122304
    published2019-02-19
    reporterThis script is Copyright (C) 2019-2020 and is owned by Tenable, Inc. or an Affiliate thereof.
    sourcehttps://www.tenable.com/plugins/nessus/122304
    titleopenSUSE Security Update : chromium (openSUSE-2019-204)
  • NASL familyMacOS X Local Security Checks
    NASL idMACOSX_GOOGLE_CHROME_72_0_3626_81.NASL
    descriptionThe version of Google Chrome installed on the remote macOS host is prior to 72.0.3626.81. It is, therefore, affected by multiple vulnerabilities as noted in Google Chrome stable channel update release notes for 2019/01/29. Please refer to the release notes for additional information. Note that Nessus has not attempted to exploit these issues but has instead relied only on the application
    last seen2020-06-01
    modified2020-06-02
    plugin id121513
    published2019-01-31
    reporterThis script is Copyright (C) 2019 and is owned by Tenable, Inc. or an Affiliate thereof.
    sourcehttps://www.tenable.com/plugins/nessus/121513
    titleGoogle Chrome < 72.0.3626.81 Multiple Vulnerabilities
  • NASL familyFedora Local Security Checks
    NASL idFEDORA_2019-561EAE4626.NASL
    descriptionUpdate to 73.0.3683.75. Fixes large bucket of CVEs. CVE-2019-5754 CVE-2019-5782 CVE-2019-5755 CVE-2019-5756 CVE-2019-5757 CVE-2019-5758 CVE-2019-5759 CVE-2019-5760 CVE-2019-5761 CVE-2019-5762 CVE-2019-5763 CVE-2019-5764 CVE-2019-5765 CVE-2019-5766 CVE-2019-5767 CVE-2019-5768 CVE-2019-5769 CVE-2019-5770 CVE-2019-5771 CVE-2019-5772 CVE-2019-5773 CVE-2019-5774 CVE-2019-5775 CVE-2019-5776 CVE-2019-5777 CVE-2019-5778 CVE-2019-5779 CVE-2019-5780 CVE-2019-5781 CVE-2019-5784 CVE-2019-5786 CVE-2019-5787 CVE-2019-5788 CVE-2019-5789 CVE-2019-5790 CVE-2019-5791 CVE-2019-5792 CVE-2019-5793 CVE-2019-5794 CVE-2019-5795 CVE-2019-5796 CVE-2019-5797 CVE-2019-5798 CVE-2019-5799 CVE-2019-5800 CVE-2019-5802 CVE-2019-5803 Note that Tenable Network Security has extracted the preceding description block directly from the Fedora update system website. 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 id123100
    published2019-03-26
    reporterThis script is Copyright (C) 2019-2020 and is owned by Tenable, Inc. or an Affiliate thereof.
    sourcehttps://www.tenable.com/plugins/nessus/123100
    titleFedora 29 : chromium (2019-561eae4626)
  • NASL familyFedora Local Security Checks
    NASL idFEDORA_2019-05A780936D.NASL
    descriptionUpdate to 73.0.3683.75. Fixes large bucket of CVEs. CVE-2019-5754 CVE-2019-5782 CVE-2019-5755 CVE-2019-5756 CVE-2019-5757 CVE-2019-5758 CVE-2019-5759 CVE-2019-5760 CVE-2019-5761 CVE-2019-5762 CVE-2019-5763 CVE-2019-5764 CVE-2019-5765 CVE-2019-5766 CVE-2019-5767 CVE-2019-5768 CVE-2019-5769 CVE-2019-5770 CVE-2019-5771 CVE-2019-5772 CVE-2019-5773 CVE-2019-5774 CVE-2019-5775 CVE-2019-5776 CVE-2019-5777 CVE-2019-5778 CVE-2019-5779 CVE-2019-5780 CVE-2019-5781 CVE-2019-5784 CVE-2019-5786 CVE-2019-5787 CVE-2019-5788 CVE-2019-5789 CVE-2019-5790 CVE-2019-5791 CVE-2019-5792 CVE-2019-5793 CVE-2019-5794 CVE-2019-5795 CVE-2019-5796 CVE-2019-5797 CVE-2019-5798 CVE-2019-5799 CVE-2019-5800 CVE-2019-5802 CVE-2019-5803 Note that Tenable Network Security has extracted the preceding description block directly from the Fedora update system website. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.
    last seen2020-05-31
    modified2019-05-02
    plugin id124466
    published2019-05-02
    reporterThis script is Copyright (C) 2019-2020 and is owned by Tenable, Inc. or an Affiliate thereof.
    sourcehttps://www.tenable.com/plugins/nessus/124466
    titleFedora 30 : chromium (2019-05a780936d)
  • NASL familyWindows
    NASL idGOOGLE_CHROME_72_0_3626_81.NASL
    descriptionThe version of Google Chrome installed on the remote Windows host is prior to 72.0.3626.81. It is, therefore, affected by multiple vulnerabilities as noted in Google Chrome stable channel update release notes for 2019/01/29. Please refer to the release notes for additional information. Note that Nessus has not attempted to exploit these issues but has instead relied only on the application
    last seen2020-06-01
    modified2020-06-02
    plugin id121514
    published2019-01-31
    reporterThis script is Copyright (C) 2019 and is owned by Tenable, Inc. or an Affiliate thereof.
    sourcehttps://www.tenable.com/plugins/nessus/121514
    titleGoogle Chrome < 72.0.3626.81 Multiple Vulnerabilities

Redhat

advisories
rhsa
idRHSA-2019:0309
rpms
  • chromium-browser-0:72.0.3626.81-1.el6_10
  • chromium-browser-debuginfo-0:72.0.3626.81-1.el6_10