Vulnerability Monitor

The vendors, products, and vulnerabilities you care about

CVE-2018-18358

Lack of special casing of localhost in WPAD files in Google Chrome prior to 71.0.3578.80 allowed an attacker on the local network segment to proxy resources on localhost via a crafted WPAD file.

Security Impact Summary

This vulnerability carries a MEDIUM severity rating with a CVSS v3.1 score of 5.7, indicating it requires adjacent network access with relatively low complexity though user interaction is required and does not require pre-existing privileges . The vulnerability impacts integrity (unauthorized modifications), for affected systems. Impacting 5 products from google, from debian, from redhat and 2 others, organizations running these solutions should prioritize assessment and patching.

Historical Context

First disclosed in 2018, this vulnerability was reported during a period defined by widespread IoT adoption challenges, mobile security concerns, and the emergence of advanced persistent threat (APT) techniques. Contemporary mitigation strategies focused on secure development practices and third-party component vetting.

Published

2018-12-11T16:29:02.090

Last Modified

2026-06-17T01:47:04.273

Status

Modified

Source

[email protected]

Severity

CVSSv3.0: 5.7 (MEDIUM)

CVSSv2 Vector

AV:A/AC:M/Au:N/C:N/I:P/A:N

Access Vector: ADJACENT_NETWORK
Access Complexity: MEDIUM
Authentication: NONE
Confidentiality Impact: NONE
Integrity Impact: PARTIAL
Availability Impact: NONE

Exploitability Score

5.5

Impact Score

2.9

Weaknesses

Type: Primary
CWE-20

Affected Vendors & Products

Type	Vendor	Product	Version/Range	Vulnerable?
Application	google	chrome	< 71.0.3578.80	Yes
Operating System	debian	debian_linux	9.0	Yes
Operating System	redhat	enterprise_linux_desktop	6.0	Yes
Operating System	redhat	enterprise_linux_server	6.0	Yes
Operating System	redhat	enterprise_linux_workstation	6.0	Yes

References

http://www.securityfocus.com/bid/106084 ([email protected])
https://access.redhat.com/errata/RHSA-2018:3803 ([email protected])
https://chromereleases.googleblog.com/2018/12/stable-channel-update-for-desktop.html ([email protected])
https://crbug.com/899126 ([email protected])
https://security.gentoo.org/glsa/201908-18 ([email protected])
https://www.debian.org/security/2018/dsa-4352 ([email protected])
http://www.securityfocus.com/bid/106084 (af854a3a-2127-422b-91ae-364da2661108)
https://access.redhat.com/errata/RHSA-2018:3803 (af854a3a-2127-422b-91ae-364da2661108)
https://chromereleases.googleblog.com/2018/12/stable-channel-update-for-desktop.html (af854a3a-2127-422b-91ae-364da2661108)
https://crbug.com/899126 (af854a3a-2127-422b-91ae-364da2661108)
https://security.gentoo.org/glsa/201908-18 (af854a3a-2127-422b-91ae-364da2661108)
https://www.debian.org/security/2018/dsa-4352 (af854a3a-2127-422b-91ae-364da2661108)

How SecUtils Interprets This CVE

SecUtils normalizes and enriches National Vulnerability Database (NVD) records by standardizing vendor and product identifiers, aggregating vulnerability metadata from both NVD and MITRE sources, and providing structured context for security teams. For google's affected products, we extract Common Platform Enumeration (CPE) data, Common Weakness Enumeration (CWE) classifications, CVSS severity metrics, and reference data to enable rapid vulnerability prioritization and asset correlation. This record contains no exploit code, proof-of-concept instructions, or attack methodologies—only defensive intelligence necessary for patch management, risk assessment, and security operations.