Linux Security
    Linux Security
    Linux Security

    Gentoo: GLSA-202007-08: Chromium, Google Chrome: Multiple vulnerabilities

    Date
    55
    Posted By
    Multiple vulnerabilities have been found in Chromium and Google Chrome, the worst of which could result in the arbitrary execution of code.
    - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    Gentoo Linux Security Advisory                           GLSA 202007-08
    - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                                               https://security.gentoo.org/
    - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    
     Severity: Normal
        Title: Chromium, Google Chrome: Multiple vulnerabilities
         Date: July 26, 2020
         Bugs: #728418, #729310, #732588
           ID: 202007-08
    
    - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    
    Synopsis
    ========
    
    Multiple vulnerabilities have been found in Chromium and Google Chrome,
    the worst of which could result in the arbitrary execution of code.
    
    Background
    ==========
    
    Chromium is an open-source browser project that aims to build a safer,
    faster, and more stable way for all users to experience the web.
    
    Google Chrome is one fast, simple, and secure browser for all your
    devices.
    
    Affected packages
    =================
    
        -------------------------------------------------------------------
         Package              /     Vulnerable     /            Unaffected
        -------------------------------------------------------------------
      1  www-client/chromium       < 84.0.4147.89         >= 84.0.4147.89
      2  www-client/google-chrome
                                   < 84.0.4147.89         >= 84.0.4147.89
        -------------------------------------------------------------------
         2 affected packages
    
    Description
    ===========
    
    Multiple vulnerabilities have been discovered in Chromium and Google
    Chrome. Please review the CVE identifiers referenced below for details.
    
    Impact
    ======
    
    Please review the referenced CVE identifiers for details.
    
    Workaround
    ==========
    
    There is no known workaround at this time.
    
    Resolution
    ==========
    
    All Chromium users should upgrade to the latest version:
    
      # emerge --sync
      # emerge --ask --oneshot -v ">=www-client/chromium-84.0.4147.89"
    
    All Google Chrome users should upgrade to the latest version:
    
      # emerge --sync
      # emerge --ask --oneshot -v ">=www-client/google-chrome-84.0.4147.89"
    
    References
    ==========
    
    [  1 ] CVE-2020-6505
           https://nvd.nist.gov/vuln/detail/CVE-2020-6505
    [  2 ] CVE-2020-6506
           https://nvd.nist.gov/vuln/detail/CVE-2020-6506
    [  3 ] CVE-2020-6507
           https://nvd.nist.gov/vuln/detail/CVE-2020-6507
    [  4 ] CVE-2020-6509
           https://nvd.nist.gov/vuln/detail/CVE-2020-6509
    [  5 ] CVE-2020-6510
           https://nvd.nist.gov/vuln/detail/CVE-2020-6510
    [  6 ] CVE-2020-6511
           https://nvd.nist.gov/vuln/detail/CVE-2020-6511
    [  7 ] CVE-2020-6512
           https://nvd.nist.gov/vuln/detail/CVE-2020-6512
    [  8 ] CVE-2020-6513
           https://nvd.nist.gov/vuln/detail/CVE-2020-6513
    [  9 ] CVE-2020-6514
           https://nvd.nist.gov/vuln/detail/CVE-2020-6514
    [ 10 ] CVE-2020-6515
           https://nvd.nist.gov/vuln/detail/CVE-2020-6515
    [ 11 ] CVE-2020-6516
           https://nvd.nist.gov/vuln/detail/CVE-2020-6516
    [ 12 ] CVE-2020-6517
           https://nvd.nist.gov/vuln/detail/CVE-2020-6517
    [ 13 ] CVE-2020-6518
           https://nvd.nist.gov/vuln/detail/CVE-2020-6518
    [ 14 ] CVE-2020-6519
           https://nvd.nist.gov/vuln/detail/CVE-2020-6519
    [ 15 ] CVE-2020-6520
           https://nvd.nist.gov/vuln/detail/CVE-2020-6520
    [ 16 ] CVE-2020-6521
           https://nvd.nist.gov/vuln/detail/CVE-2020-6521
    [ 17 ] CVE-2020-6522
           https://nvd.nist.gov/vuln/detail/CVE-2020-6522
    [ 18 ] CVE-2020-6523
           https://nvd.nist.gov/vuln/detail/CVE-2020-6523
    [ 19 ] CVE-2020-6524
           https://nvd.nist.gov/vuln/detail/CVE-2020-6524
    [ 20 ] CVE-2020-6525
           https://nvd.nist.gov/vuln/detail/CVE-2020-6525
    [ 21 ] CVE-2020-6526
           https://nvd.nist.gov/vuln/detail/CVE-2020-6526
    [ 22 ] CVE-2020-6527
           https://nvd.nist.gov/vuln/detail/CVE-2020-6527
    [ 23 ] CVE-2020-6528
           https://nvd.nist.gov/vuln/detail/CVE-2020-6528
    [ 24 ] CVE-2020-6529
           https://nvd.nist.gov/vuln/detail/CVE-2020-6529
    [ 25 ] CVE-2020-6530
           https://nvd.nist.gov/vuln/detail/CVE-2020-6530
    [ 26 ] CVE-2020-6531
           https://nvd.nist.gov/vuln/detail/CVE-2020-6531
    [ 27 ] CVE-2020-6533
           https://nvd.nist.gov/vuln/detail/CVE-2020-6533
    [ 28 ] CVE-2020-6534
           https://nvd.nist.gov/vuln/detail/CVE-2020-6534
    [ 29 ] CVE-2020-6535
           https://nvd.nist.gov/vuln/detail/CVE-2020-6535
    [ 30 ] CVE-2020-6536
           https://nvd.nist.gov/vuln/detail/CVE-2020-6536
    
    Availability
    ============
    
    This GLSA and any updates to it are available for viewing at
    the Gentoo Security Website:
    
     https://security.gentoo.org/glsa/202007-08
    
    Concerns?
    =========
    
    Security is a primary focus of Gentoo Linux and ensuring the
    confidentiality and security of our users' machines is of utmost
    importance to us. Any security concerns should be addressed to
    This email address is being protected from spambots. You need JavaScript enabled to view it. or alternatively, you may file a bug at
    https://bugs.gentoo.org.
    
    License
    =======
    
    Copyright 2020 Gentoo Foundation, Inc; referenced text
    belongs to its owner(s).
    
    The contents of this document are licensed under the
    Creative Commons - Attribution / Share Alike license.
    
    https://creativecommons.org/licenses/by-sa/2.5
    

    Advisories

    LinuxSecurity Poll

    How are you contributing to Open Source?

    No answer selected. Please try again.
    Please select either existing option or enter your own, however not both.
    Please select minimum 0 answer(s) and maximum 4 answer(s).
    /main-polls/37-how-are-you-contributing-to-open-source?task=poll.vote&format=json
    37
    radio
    [{"id":"127","title":"I'm involved with the development of an open-source project(s).","votes":"1","type":"x","order":"1","pct":100,"resources":[]},{"id":"128","title":"I've reported vulnerabilities I've discovered in open-source code.","votes":"0","type":"x","order":"2","pct":0,"resources":[]},{"id":"129","title":"I've provided developers with feedback on their projects.","votes":"0","type":"x","order":"3","pct":0,"resources":[]},{"id":"130","title":"I've helped another community member get started contributing to Open Source.","votes":"0","type":"x","order":"4","pct":0,"resources":[]}] ["#ff5b00","#4ac0f2","#b80028","#eef66c","#60bb22","#b96a9a","#62c2cc"] ["rgba(255,91,0,0.7)","rgba(74,192,242,0.7)","rgba(184,0,40,0.7)","rgba(238,246,108,0.7)","rgba(96,187,34,0.7)","rgba(185,106,154,0.7)","rgba(98,194,204,0.7)"] 350


    VIEW MORE POLLS

    bottom 200

    Please enable / Bitte aktiviere JavaScript!
    Veuillez activer / Por favor activa el Javascript![ ? ]

    We use cookies to provide and improve our services. By using our site, you consent to our Cookie Policy.