Bug 1608204 (CVE-2018-16064)

Summary:	CVE-2018-16064 chromium-browser: Request privilege escalation in Extensions
Product:	[Other] Security Response	Reporter:	Sam Fowler <sfowler>
Component:	vulnerability	Assignee:	Red Hat Product Security <security-response-team>
Status:	CLOSED ERRATA	QA Contact:
Severity:	low	Docs Contact:
Priority:	low
Version:	unspecified	CC:	akarshan.biswas, mhroncok, nsl, sfowler, tcallawa, tpopela, yaneti
Target Milestone:	---	Keywords:	Security
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	chromium-browser 68.0.3440.75	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-07-30 19:32:19 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1608209, 1608210, 1608211
Bug Blocks:	1608214

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.