Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1656561 (CVE-2018-18347) - CVE-2018-18347 chromium-browser: Inappropriate implementation in Navigation
Summary: CVE-2018-18347 chromium-browser: Inappropriate implementation in Navigation
Keywords:
Status: CLOSED ERRATA
Alias: CVE-2018-18347
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 1656574 1656575 1656576
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-12-05 18:23 UTC by Pedro Sampaio
Modified: 2021-02-16 22:41 UTC (History)
4 users (show)

Fixed In Version: chromium-browser 71.0.3578.80
Clone Of:
Environment:
Last Closed: 2018-12-10 21:44:56 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2018:3803 0 None None None 2018-12-10 10:33:03 UTC

Description Pedro Sampaio 2018-12-05 18:23:18 UTC 
An inappropriate implementation flaw was found in the Navigation component of the Chromium browser.

Upstream bug(s):

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

External References:

https://chromereleases.googleblog.com/2018/12/stable-channel-update-for-desktop.html
Comment 1 Pedro Sampaio 2018-12-05 18:31:51 UTC 
Created chromium tracking bugs for this issue:

Affects: epel-7 [bug 1656576]
Affects: fedora-all [bug 1656575]
Comment 3 errata-xmlrpc 2018-12-10 10:33:00 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 6 Supplementary

Via RHSA-2018:3803 https://access.redhat.com/errata/RHSA-2018:3803
Note You need to log in before you can comment on or make changes to this bug.