CVE-2018-18353: Medium severity google chrome vulnerability

Published Dec 5, 2018
·
Updated

An inappropriate implementation flaw was found in the Network Authentication component of the Chromium browser.

Upstream bug(s):

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

External References:

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

Other sources

Failure to dismiss http auth dialogs on navigation in Network Authentication in Google Chrome on Android prior to 71.0.3578.80 allowed a remote attacker to confuse the user about the origin of an auto dialog via a crafted HTML page.

Affected Software

8 affected componentsFixes available
debian/chromium
90.0.4430.212-1~deb10u1116.0.5845.180-1~deb11u1120.0.6099.129-1~deb11u1119.0.6045.199-1~deb12u1120.0.6099.129-1~deb12u1120.0.6099.129-1
redhat/chromium-browser<71.0.3578.80
71.0.3578.80
Google Chrome<71.0.3578.80
Google Android
redhat Enterprise Linux Desktop=6.0
redhat Enterprise Linux Server=6.0
redhat Enterprise Linux Workstation=6.0
Debian Debian Linux=9.0

Event History

Dec 11, 2018
CVE Published
via MITRE·03:00 PM
Data Sourced
via MITRE·03:00 PM
DescriptionWeakness
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2018-18353?

CVE-2018-18353 is classified as a medium-severity vulnerability due to its potential impact on user security.

2

How do I fix CVE-2018-18353?

To fix CVE-2018-18353, update your Chromium browser to version 90.0.4430.212 or later for Debian systems, or to version 71.0.3578.80 or later for Red Hat systems.

3

Which software is affected by CVE-2018-18353?

CVE-2018-18353 affects multiple versions of the Chromium browser as well as Google Chrome versions up to 71.0.3578.80.

4

What causes the issue in CVE-2018-18353?

CVE-2018-18353 is caused by an inappropriate implementation flaw in the Network Authentication component of the Chromium browser.

5

Is there a workaround for CVE-2018-18353?

There are no known workarounds for CVE-2018-18353, so updating to a fixed version is recommended.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203