Bug 1608204 (CVE-2018-16064) - CVE-2018-16064 chromium-browser: Request privilege escalation in Extensions
Summary: CVE-2018-16064 chromium-browser: Request privilege escalation in Extensions
Keywords:
Status: CLOSED ERRATA
Alias: CVE-2018-16064
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 1608209 1608210 1608211
Blocks: 1608214
TreeView+ depends on / blocked
 
Reported: 2018-07-25 06:25 UTC by Sam Fowler
Modified: 2021-02-16 23:53 UTC (History)
7 users (show)

Fixed In Version: chromium-browser 68.0.3440.75
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-07-30 19:32:19 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2018:2282 0 None None None 2018-07-30 15:12:31 UTC

Description Sam Fowler 2018-07-25 06:25:20 UTC 
A request privilege escalation flaw was found in the Extensions  component of the Chromium browser.

Upstream bug(s):

https://code.google.com/p/chromium/issues/detail?id=797461

External References:

https://chromereleases.googleblog.com/2018/07/stable-channel-update-for-desktop.html
Comment 1 Sam Fowler 2018-07-25 06:28:37 UTC 
Created chromium tracking bugs for this issue:

Affects: epel-7 [bug 1608211]
Affects: fedora-all [bug 1608210]
Comment 3 errata-xmlrpc 2018-07-30 15:12:25 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 6 Supplementary

Via RHSA-2018:2282 https://access.redhat.com/errata/RHSA-2018:2282
Comment 4 Nicholas Luedtke 2019-08-08 15:09:36 UTC 
Looks like the alias might be wrong. According to the linked bug page the correct CVE is CVE-2018-16064 not CVE-2018-6044. This is confirmed by the NVD page https://nvd.nist.gov/vuln/detail/CVE-2018-16064. 

It appears the Chrome release note just mentioned the wrong CVE id.
Comment 5 Sam Fowler 2019-08-09 05:19:18 UTC 
(In reply to Nicholas Luedtke from comment #4)
> Looks like the alias might be wrong. According to the linked bug page the
> correct CVE is CVE-2018-16064 not CVE-2018-6044. This is confirmed by the
> NVD page https://nvd.nist.gov/vuln/detail/CVE-2018-16064. 
> 
> It appears the Chrome release note just mentioned the wrong CVE id.

Thanks for the info. CVE ID changed from CVE-2018-6044 to CVE-2018-16064.
Note You need to log in before you can comment on or make changes to this bug.