CVE-2018-18506
What it is
When proxy auto-detection is enabled, if a web server serves a Proxy Auto-Configuration (PAC) file or if a PAC file is loaded locally, this PAC file can specify that requests to the localhost are to be sent through the proxy to another server. This behavior is disallowed by default when a proxy is manually configured, but when enabled could allow for attacks on services and tools that bind to the localhost for networked behavior if they are accessed through browsing. This vulnerability affects Firefox < 65.
At a glance
- Exploitability
- Can be exploited over the network without logging in. High risk of data tampering.
- Exploit odds
- 2.2% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 2.2% in the next 30 days (EPSS).
- Severity: 5.9 MEDIUM (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 2.2% · EPSS, next 30 days
- Record status
- Modified
Affected
- Mozilla Firefox < 65.0
- Canonical Ubuntu Linux 14.04
- Canonical Ubuntu Linux 16.04
- Canonical Ubuntu Linux 18.04
- Canonical Ubuntu Linux 18.10
- Debian Linux 8.0
- Debian Linux 9.0
- Redhat Enterprise Linux 8.0
Attack profile CVSS 3.1 · 5.9
- Attack vector
- Network
- Complexity
- High
- Privileges needed
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
Raw vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2018-18506.md and follow it. Check whether this project is affected by CVE-2018-18506. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://www.mozilla.org/security/advisories/mfsa2019-01/
- https://www.mozilla.org/security/advisories/mfsa2019-01/
References
- http://lists.opensuse.org/opensuse-security-announce/2019-03/msg00035.html
- http://lists.opensuse.org/opensuse-security-announce/2019-03/msg00043.html
- http://lists.opensuse.org/opensuse-security-announce/2019-04/msg00023.html
- http://lists.opensuse.org/opensuse-security-announce/2019-04/msg00043.html
- http://www.securityfocus.com/bid/106773
- https://access.redhat.com/errata/RHSA-2019:0622
- https://access.redhat.com/errata/RHSA-2019:0623
- https://access.redhat.com/errata/RHSA-2019:0680
- https://access.redhat.com/errata/RHSA-2019:0681
- https://access.redhat.com/errata/RHSA-2019:0966
- https://access.redhat.com/errata/RHSA-2019:1144
- https://lists.debian.org/debian-lts-announce/2019/03/msg00024.html
- https://lists.debian.org/debian-lts-announce/2019/04/msg00000.html
- https://seclists.org/bugtraq/2019/Apr/0
- https://seclists.org/bugtraq/2019/Mar/28
- https://security.gentoo.org/glsa/201904-07
- https://usn.ubuntu.com/3874-1/
- https://usn.ubuntu.com/3927-1/
- https://www.debian.org/security/2019/dsa-4411
- https://www.debian.org/security/2019/dsa-4420
- https://www.mozilla.org/security/advisories/mfsa2019-01/
- http://lists.opensuse.org/opensuse-security-announce/2019-03/msg00035.html
- http://lists.opensuse.org/opensuse-security-announce/2019-03/msg00043.html
- http://lists.opensuse.org/opensuse-security-announce/2019-04/msg00023.html
- http://lists.opensuse.org/opensuse-security-announce/2019-04/msg00043.html