Bug 1670599

Summary: chromium-browser: Insufficient policy enforcement in Omnibox
Product: [Other] Security Response Reporter: Pedro Sampaio <psampaio>
Component: vulnerabilityAssignee: Red Hat Product Security <security-response-team>
Status: CLOSED DUPLICATE QA Contact:
Severity: low Docs Contact:
Priority: low    
Version: unspecifiedCC: erack, tcallawa, tpopela, yaneti
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: chromium-browser 72.0.3626.81 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-01-31 12:20:27 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: 1670600, 1670601, 1670602    
Bug Blocks: 1670603    

Description Pedro Sampaio 2019-01-29 21:30:46 UTC
An insufficient policy enforcement flaw was found in the Omnibox component of the Chromium browser.

Upstream bug(s):

https://code.google.com/p/chromium/issues/detail?id=914497
https://code.google.com/p/chromium/issues/detail?id=913296
https://code.google.com/p/chromium/issues/detail?id=895152
https://code.google.com/p/chromium/issues/detail?id=915469
https://code.google.com/p/chromium/issues/detail?id=913970
https://code.google.com/p/chromium/issues/detail?id=912211
https://code.google.com/p/chromium/issues/detail?id=912074
https://code.google.com/p/chromium/issues/detail?id=904714
https://code.google.com/p/chromium/issues/detail?id=900552
https://code.google.com/p/chromium/issues/detail?id=914731
https://code.google.com/p/chromium/issues/detail?id=913246
https://code.google.com/p/chromium/issues/detail?id=922677
https://code.google.com/p/chromium/issues/detail?id=922627
https://code.google.com/p/chromium/issues/detail?id=916080
https://code.google.com/p/chromium/issues/detail?id=912947
https://code.google.com/p/chromium/issues/detail?id=912520
https://code.google.com/p/chromium/issues/detail?id=899689
https://code.google.com/p/chromium/issues/detail?id=907047
https://code.google.com/p/chromium/issues/detail?id=902427
https://code.google.com/p/chromium/issues/detail?id=805557
https://code.google.com/p/chromium/issues/detail?id=913975
https://code.google.com/p/chromium/issues/detail?id=908749
https://code.google.com/p/chromium/issues/detail?id=904265
https://code.google.com/p/chromium/issues/detail?id=908292
https://code.google.com/p/chromium/issues/detail?id=917668
https://code.google.com/p/chromium/issues/detail?id=904182
https://code.google.com/p/chromium/issues/detail?id=896722
https://code.google.com/p/chromium/issues/detail?id=863663
https://code.google.com/p/chromium/issues/detail?id=849421
https://code.google.com/p/chromium/issues/detail?id=918470
https://code.google.com/p/chromium/issues/detail?id=904219
https://code.google.com/p/chromium/issues/detail?id=891697
https://code.google.com/p/chromium/issues/detail?id=896725

External References:

https://chromereleases.googleblog.com/2019/01/stable-channel-update-for-desktop.html

Comment 1 Pedro Sampaio 2019-01-29 21:31:24 UTC
Created chromium tracking bugs for this issue:

Affects: epel-7 [bug 1670602]
Affects: fedora-all [bug 1670601]

Comment 3 Andrej Nemec 2019-01-31 12:20:27 UTC

*** This bug has been marked as a duplicate of bug 1670771 ***