CVE-2019-5775: Insufficient policy enforcement in Omnibox
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=896722
External References:
https://chromereleases.googleblog.com/2019/01/stable-channel-update-for-desktop.html
Other sources
Incorrect handling of a confusable character in Omnibox in Google Chrome prior to 72.0.3626.81 allowed a remote attacker to spoof the contents of the Omnibox (URL bar) via a crafted domain name.
Credit
Affected Software
Remediation
Patch Available
Event History
Peer vulnerabilities
Found alongside the following vulnerabilities.
- CVE-2019-5754
- CVE-2019-5782
- CVE-2019-5755
- CVE-2019-5756
- CVE-2019-5757
- CVE-2019-5758
- CVE-2019-5759
- CVE-2019-5760
- CVE-2019-5761
- CVE-2019-5762
- CVE-2019-5763
- CVE-2019-5764
- CVE-2019-13768
- CVE-2019-5765
- CVE-2019-5785
- CVE-2019-5766
- CVE-2019-5767
- CVE-2019-5768
- CVE-2019-5769
- CVE-2019-5770
- CVE-2019-5771
- CVE-2019-5772
- CVE-2019-5773
- CVE-2019-5774
- CVE-2019-5776
- CVE-2019-5777
- CVE-2018-20073
- CVE-2019-5778
- CVE-2019-5779
- CVE-2019-5780
- CVE-2019-5783
- CVE-2019-5781
- CVE-2019-13684
Frequently Asked Questions
What is the severity of CVE-2019-5775?
CVE-2019-5775 has been classified with a medium severity level due to its insufficient policy enforcement flaw.
How do I fix CVE-2019-5775?
To fix CVE-2019-5775, update your Chromium or Chrome browser to the latest version, specifically 72.0.3626.81 or later.
Which software is affected by CVE-2019-5775?
CVE-2019-5775 affects various Chromium-based browsers, including Google Chrome and the Debian version of Chromium.
Is CVE-2019-5775 present in older versions of Chromium?
Yes, CVE-2019-5775 is present in Chromium versions prior to 72.0.3626.81.
Can CVE-2019-5775 be exploited remotely?
Yes, CVE-2019-5775 can potentially be exploited remotely due to its nature of insufficient policy enforcement.