Bug 1552485 – CVE-2018-6068 chromium-browser: object lifecycle issues in chrome custom tab

Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.

Bug 1552485 - (CVE-2018-6068) CVE-2018-6068 chromium-browser: object lifecycle issues in chrome custom tab

Summary:	CVE-2018-6068 chromium-browser: object lifecycle issues in chrome custom tab

Status:	CLOSED NOTABUG

Aliases:	CVE-2018-6068

Product:	Security Response
Classification:	Other
Component:	vulnerability (Show other bugs)
Sub Component:
Version:	unspecified
Hardware:	All Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Red Hat Product Security
QA Contact:
Docs Contact:

URL:
Whiteboard:	impact=moderate,public=20180306,repor...
Keywords:	Security

Depends On:
Blocks:	1552510
	Show dependency tree / graph

Reported:	2018-03-07 03:29 EST by Andrej Nemec
Modified:	2018-03-12 06:18 EDT (History)
CC List:	3 users (show)

See Also:
Fixed In Version:	chromium-browser 65.0.3325.146
Doc Type:	If docs needed, set a value
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2018-03-12 06:07:54 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Andrej Nemec 2018-03-07 03:29:29 EST

An object lifecycle issues flaw was found in the Chrome Custom Tab component of the Chromium browser.

Upstream bug(s):

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

External References:

https://chromereleases.googleblog.com/2018/03/stable-channel-update-for-desktop.html

Comment 1 Andrej Nemec 2018-03-07 03:34:57 EST

Created chromium tracking bugs for this issue:

Affects: fedora-all [bug 1552502]
Affects: epel-7 [bug 1552504]

Comment 3 Tomas Hoger 2018-03-12 06:07:54 EDT

Chrome Custom Tab is a feature of the Android version of Chrome, so this issue should not be applicable to Chrome/Chromium versions on other operating systems.

Note You need to log in before you can comment on or make changes to this bug.