CVE-2017-5384
Proxy Auto-Config (PAC) files can specify a JavaScript function called for all URL requests with...
Proxy Auto-Config (PAC) files can specify a JavaScript function called for all URL requests with the full URL path which exposes more information than would be sent to the proxy itself in the case of HTTPS. Normally the Proxy Auto-Config file is specified by the user or machine owner and presumed to be non-malicious, but if a user has enabled Web Proxy Auto Detect (WPAD) this file can be served remotely. This vulnerability affects Firefox < 51.
Attack profile
How easy it is to exploit
- Attack vector
- Network
- Complexity
- High
- Privileges needed
- None
- User interaction
- None
What an attacker can affect
- Confidentiality
- High
- Integrity
- None
- Availability
- None
Exploit likelihood
What each source reports
NVD Score used
5.9
Proxy Auto-Config (PAC) files can specify a JavaScript function called for all URL requests with the full URL path which exposes more information than would be sent to the proxy itself in the case of HTTPS. Normally the Proxy Auto-Config file is specified by the user or machine owner and presumed to be non-malicious, but if a user has enabled Web Proxy Auto Detect (WPAD) this file can be served remotely. This vulnerability affects Firefox < 51.
- Record
CVE-2017-5384- CVSS 3.0
- 5.9 Medium
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N - CVSS 2.0
- 4.3 Medium
AV:N/AC:M/Au:N/C:P/I:N/A:N - Weakness
- CWE-200
- Updated
- 2026-11-02
CVE List No score
Proxy Auto-Config (PAC) files can specify a JavaScript function called for all URL requests with the full URL path which exposes more information than would be sent to the proxy itself in the case of HTTPS. Normally the Proxy Auto-Config file is specified by the user or machine owner and presumed to be non-malicious, but if a user has enabled Web Proxy Auto Detect (WPAD) this file can be served remotely. This vulnerability affects Firefox < 51.
- Record
CVE-2017-5384- Updated
- 2026-11-02
EUVDEUVD-2017-14488 No score
Proxy Auto-Config (PAC) files can specify a JavaScript function called for all URL requests with the full URL path which exposes more information than would be sent to the proxy itself in the case of HTTPS. Normally the Proxy Auto-Config file is specified by the user or machine owner and presumed to be non-malicious, but if a user has enabled Web Proxy Auto Detect (WPAD) this file can be served remotely. This vulnerability affects Firefox < 51.
- Record
EUVD-2017-14488- Updated
- 2026-11-03
GitHub AdvisoriesGHSA-4f25-w4cj-3v45
5.9
Proxy Auto-Config (PAC) files can specify a JavaScript function called for all URL requests with...
Proxy Auto-Config (PAC) files can specify a JavaScript function called for all URL requests with the full URL path which exposes more information than would be sent to the proxy itself in the case of HTTPS. Normally the Proxy Auto-Config file is specified by the user or machine owner and presumed to be non-malicious, but if a user has enabled Web Proxy Auto Detect (WPAD) this file can be served remotely. This vulnerability affects Firefox < 51.
- Record
GHSA-4f25-w4cj-3v45- CVSS 3.0
- 5.9 Medium
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N - Weakness
- CWE-200
- Updated
- 2026-11-02
OSVUBUNTU-CVE-2017-5384
5.9
Proxy Auto-Config (PAC) files can specify a JavaScript function called for all URL requests with the full URL path which exposes more information than would be sent to the proxy itself in the case of HTTPS. Normally the Proxy Auto-Config file is specified by the user or machine owner and presumed to be non-malicious, but if a user has enabled Web Proxy Auto Detect (WPAD) this file can be served remotely. This vulnerability affects Firefox < 51.
- Record
UBUNTU-CVE-2017-5384- CVSS 3.0
- 5.9 Medium
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N - Updated
- 2026-11-02
OSVMGASA-2017-0323 No score
Updated iceape packages fix security vulnerabilities
Updated Iceape packages include security fixes from upstream Seamonkey:
Multiple flaws were found in the way Iceape 2.46 processes various types of web content, where loading a web page containing malicious content could cause Iceape to crash, execute arbitrary code, or disclose sensitive information. (CVE-2016-5287, CVE-2016-5288, CVE-2016-5289, CVE-2016-5290, CVE-2016-5292, CVE-2016-5297, CVE-2016-9064, CVE-2016-9066, CVE-2016-9067, CVE-2016-9068, CVE-2016-9075, CVE-2016-9077, CVE-2016-5291, CVE-2016-9063, CVE-2016-9070, CVE-2016-9071, CVE-2016-9073, CVE-2016-9076, CVE-2016-9078, CVE-2016-9080, CVE-2016-9893, CVE-2016-9894, CVE-2016-9895, CVE-2016-9896, CVE-2016-9897, CVE-2016-9898, CVE-2016-9899, CVE-2016-9900, CVE-2016-9901, CVE-2016-9902, CVE-2016-9903, CVE-2016-9904, CVE-2017-5373, CVE-2017-5374, CVE-2017-5375, CVE-2017-5376, CVE-2017-5377, CVE-2017-5378, CVE-2017-5379, CVE-2017-5380, CVE-2017-5381, CVE-2017-5382, CVE-2017-5383, CVE-2017-5384, CVE-2017-5385, CVE-2017-5386, CVE-2017-5387, CVE-2017-5388, CVE-2017-5389, CVE-2017-5390, CVE-2017-5391, CVE-2017-5393, CVE-2017-5396)
- Record
MGASA-2017-0323- Updated
- 2026-11-02
OSVopenSUSE-SU-2024:10600-1 No score
MozillaFirefox-92.0-1.2 on GA media
These are all security issues fixed in the MozillaFirefox-92.0-1.2 package on the GA media of openSUSE Tumbleweed.
- Record
openSUSE-SU-2024:10600-1- Updated
- 2026-11-02
OSVopenSUSE-SU-2024:14572-1 No score
firefox-esr-128.5.1-1.1 on GA media
These are all security issues fixed in the firefox-esr-128.5.1-1.1 package on the GA media of openSUSE Tumbleweed.
- Record
openSUSE-SU-2024:14572-1- Updated
- 2026-11-02
OSVUSN-3175-1 No score
firefox vulnerabilities
Multiple memory safety issues were discovered in Firefox. If a user were tricked in to opening a specially crafted website, an attacker could potentially exploit these to cause a denial of service via application crash, or execute arbitrary code. (CVE-2017-5373, CVE-2017-5374)
JIT code allocation can allow a bypass of ASLR protections in some circumstances. If a user were tricked in to opening a specially crafted website, an attacker could potentially exploit this to cause a denial of service via application crash, or execute arbitrary code. (CVE-2017-5375)
Nicolas Grégoire discovered a use-after-free when manipulating XSL in XSLT documents in some circumstances. If a user were tricked in to opening a specially crafted website, an attacker could potentially exploit this to cause a denial of service via application crash, or execute arbitrary code. (CVE-2017-5376)
Atte Kettunen discovered a memory corruption issue in Skia in some circumstances. If a user were tricked in to opening a specially crafted website, an attacker could potentially exploit this to cause a denial of service via application crash, or execute arbitrary code. (CVE-2017-5377)
Jann Horn discovered that an object's address could be discovered through hashed codes of JavaScript objects shared between pages. If a user were tricked in to opening a specially crafted website, an attacker could potentially exploit this to obtain sensitive information. (CVE-2017-5378)
A use-after-free was discovered in Web Animations in some circumstances. If a user were tricked in to opening a specially crafted website, an attacker could potentially exploit this to cause a denial of service via application crash, or execute arbitrary code. (CVE-2017-5379)
A use-after-free was discovered during DOM manipulation of SVG content in some circumstances. If a user were tricked in to opening a specially crafted website, an attacker could potentially exploit this to cause a denial of service via application crash, or execute arbitrary code. (CVE-2017-5380)
Jann Horn discovered that the "export" function in the Certificate Viewer can force local filesystem navigation when the Common Name contains slashes. If a user were tricked in to exporting a specially crafted certificate, an attacker could potentially exploit this to save content with arbitrary filenames in unsafe locations. (CVE-2017-5381)
Jerri Rice discovered that the Feed preview for RSS feeds can be used to capture errors and exceptions generated by privileged content. An attacker could potentially exploit this to obtain sensitive information. (CVE-2017-5382)
Armin Razmjou discovered that certain unicode glyphs do not trigger punycode display. An attacker could potentially exploit this to spoof the URL bar contents. (CVE-2017-5383)
Paul Stone and Alex Chapman discovered that the full URL path is exposed to JavaScript functions specified by Proxy Auto-Config (PAC) files. If a user has enabled Web Proxy Auto Detect (WPAD), an attacker could potentially exploit this to obtain sensitive information. (CVE-2017-5384)
Muneaki Nishimura discovered that data sent in multipart channels will ignore the Referrer-Policy response headers. An attacker could potentially exploit this to obtain sensitive information. (CVE-2017-5385)
Muneaki Nishimura discovered that WebExtensions can affect other extensions using the data: protocol. If a user were tricked in to installing a specially crafted addon, an attacker could potentially exploit this to obtain sensitive information or gain additional privileges. (CVE-2017-5386)
Mustafa Hasan discovered that the existence of local files can be determined using the <track> element. An attacker could potentially exploit this to obtain sensitive information. (CVE-2017-5387)
Cullen Jennings discovered that WebRTC can be used to generate large amounts of UDP traffic. An attacker could potentially exploit this to conduct Distributed Denial-of-Service (DDOS) attacks. (CVE-2017-5388)
Kris Maglione…
- Record
USN-3175-1- Updated
- 2026-11-02
Affected products
Affected packages
| Package | Affected | Fixed |
|---|---|---|
iceapeMageia:5 |
before 2.48-1.mga5 | 2.48-1.mga5 |
iceapeMageia:6 |
before 2.48-1.mga6 | 2.48-1.mga6 |
firefoxUbuntu:14.04:LTS |
before 51.0.1+build2-0ubuntu0.14.04.1, plus listed versions 24.0+build1-0ubuntu125.0+build3-0ubuntu0.13.10.128.0~b2+build1-0ubuntu228.0+build1-0ubuntu128.0+build2-0ubuntu1 Show 43 moreShow less28.0+build2-0ubuntu229.0+build1-0ubuntu0.14.04.230.0+build1-0ubuntu0.14.04.331.0+build1-0ubuntu0.14.04.132.0+build1-0ubuntu0.14.04.132.0.3+build1-0ubuntu0.14.04.133.0+build2-0ubuntu0.14.04.134.0+build2-0ubuntu0.14.04.135.0+build3-0ubuntu0.14.04.235.0.1+build1-0ubuntu0.14.04.136.0+build2-0ubuntu0.14.04.436.0.1+build2-0ubuntu0.14.04.136.0.4+build1-0ubuntu0.14.04.137.0+build2-0ubuntu0.14.04.137.0.1+build1-0ubuntu0.14.04.137.0.2+build1-0ubuntu0.14.04.138.0+build3-0ubuntu0.14.04.139.0+build5-0ubuntu0.14.04.139.0.3+build2-0ubuntu0.14.04.140.0+build4-0ubuntu0.14.04.140.0+build4-0ubuntu0.14.04.440.0.3+build1-0ubuntu0.14.04.141.0+build3-0ubuntu0.14.04.141.0.1+build2-0ubuntu0.14.04.141.0.2+build2-0ubuntu0.14.04.142.0+build2-0ubuntu0.14.04.143.0+build1-0ubuntu0.14.04.143.0.4+build3-0ubuntu0.14.04.144.0+build3-0ubuntu0.14.04.144.0.1+build2-0ubuntu0.14.04.144.0.2+build1-0ubuntu0.14.04.145.0+build2-0ubuntu0.14.04.145.0.1+build1-0ubuntu0.14.04.245.0.2+build1-0ubuntu0.14.04.146.0+build5-0ubuntu0.14.04.246.0.1+build1-0ubuntu0.14.04.347.0+build3-0ubuntu0.14.04.148.0+build2-0ubuntu0.14.04.149.0+build4-0ubuntu0.14.04.149.0.2+build2-0ubuntu0.14.04.150.0+build2-0ubuntu0.14.04.250.0.2+build1-0ubuntu0.14.04.150.1.0+build2-0ubuntu0.14.04.1 |
51.0.1+build2-0ubuntu0.14.04.1 |
firefoxUbuntu:16.04:LTS |
before 51.0.1+build2-0ubuntu0.16.04.1, plus listed versions 41.0.2+build2-0ubuntu142.0+build2-0ubuntu144.0+build3-0ubuntu244.0.1+build1-0ubuntu144.0.2+build1-0ubuntu1 Show 12 moreShow less45.0+build2-0ubuntu145.0.1+build1-0ubuntu145.0.2+build1-0ubuntu146.0+build5-0ubuntu0.16.04.246.0.1+build1-0ubuntu0.16.04.247.0+build3-0ubuntu0.16.04.148.0+build2-0ubuntu0.16.04.149.0+build4-0ubuntu0.16.04.149.0.2+build2-0ubuntu0.16.04.250.0+build2-0ubuntu0.16.04.250.0.2+build1-0ubuntu0.16.04.150.1.0+build2-0ubuntu0.16.04.1 |
51.0.1+build2-0ubuntu0.16.04.1 |
MozillaFirefoxopenSUSE:Tumbleweed |
before 92.0-1.2 | 92.0-1.2 |
firefox-esropenSUSE:Tumbleweed |
before 128.5.1-1.1 | 128.5.1-1.1 |
History
| Recorded | Changed | Sources |
|---|---|---|
| aliases | EUVD | |
| first indexed | CVE List, GitHub Advisories, NVD, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
CVE-2017-5384 is a medium vulnerability (CVSS 5.9) in Mozilla Firefox, published January 25, 2017. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 1.47%, the 73rd percentile. Fixed in iceape 2.48-1.mga5.
References
contextis.com//resources/blog/leaking-https-urls-20-year-old-vulnerability
bugzilla.mozilla.org/show_bug.cgi?id=1255474
securitytracker.com/id/1037693
mozilla.org/security/advisories/mfsa2017-01
securityfocus.com/bid/95763
nvd.nist.gov/vuln/detail/CVE-2017-5384
Show 194 moreShow less
github.com/advisories/GHSA-4f25-w4cj-3v45
advisories.mageia.org/MGASA-2017-0323.html
bugs.mageia.org/show_bug.cgi?id=21637
mozilla.org/en-US/security/advisories/mfsa2016-87
mozilla.org/en-US/security/advisories/mfsa2016-89
mozilla.org/en-US/security/advisories/mfsa2016-91
mozilla.org/en-US/security/advisories/mfsa2016-94
mozilla.org/en-US/security/advisories/mfsa2017-01
ubuntu.com/security/CVE-2017-5384
ubuntu.com/security/notices/USN-3175-1
cve.org/CVERecord?id=CVE-2017-5384
ubuntu.com/security/CVE-2017-5373
ubuntu.com/security/CVE-2017-5374
ubuntu.com/security/CVE-2017-5375
ubuntu.com/security/CVE-2017-5376
ubuntu.com/security/CVE-2017-5377
ubuntu.com/security/CVE-2017-5378
ubuntu.com/security/CVE-2017-5379
ubuntu.com/security/CVE-2017-5380
ubuntu.com/security/CVE-2017-5381
ubuntu.com/security/CVE-2017-5382
ubuntu.com/security/CVE-2017-5383
ubuntu.com/security/CVE-2017-5385
ubuntu.com/security/CVE-2017-5386
ubuntu.com/security/CVE-2017-5387
ubuntu.com/security/CVE-2017-5388
ubuntu.com/security/CVE-2017-5389
ubuntu.com/security/CVE-2017-5390
ubuntu.com/security/CVE-2017-5391
ubuntu.com/security/CVE-2017-5393
ubuntu.com/security/CVE-2017-5396
suse.com/security/cve/CVE-2006-6077
suse.com/security/cve/CVE-2007-0008
suse.com/security/cve/CVE-2007-0009
suse.com/security/cve/CVE-2007-0078
suse.com/security/cve/CVE-2007-0079
suse.com/security/cve/CVE-2007-0775
suse.com/security/cve/CVE-2007-0776
suse.com/security/cve/CVE-2007-0777
suse.com/security/cve/CVE-2007-0780
suse.com/security/cve/CVE-2007-0800
suse.com/security/cve/CVE-2007-0981
suse.com/security/cve/CVE-2007-0995
suse.com/security/cve/CVE-2007-0996
suse.com/security/cve/CVE-2007-3089
suse.com/security/cve/CVE-2007-3285
suse.com/security/cve/CVE-2007-3656
suse.com/security/cve/CVE-2007-3670
suse.com/security/cve/CVE-2007-3734
suse.com/security/cve/CVE-2007-3735
suse.com/security/cve/CVE-2007-3736
suse.com/security/cve/CVE-2007-3737
suse.com/security/cve/CVE-2007-3738
suse.com/security/cve/CVE-2008-0412
suse.com/security/cve/CVE-2008-0414
suse.com/security/cve/CVE-2008-0415
suse.com/security/cve/CVE-2008-0417
suse.com/security/cve/CVE-2008-0418
suse.com/security/cve/CVE-2008-0419
suse.com/security/cve/CVE-2008-0591
suse.com/security/cve/CVE-2008-0592
suse.com/security/cve/CVE-2008-0593
suse.com/security/cve/CVE-2008-0594
suse.com/security/cve/CVE-2008-4063
suse.com/security/cve/CVE-2009-0352
suse.com/security/cve/CVE-2009-0354
suse.com/security/cve/CVE-2009-0355
suse.com/security/cve/CVE-2009-0356
suse.com/security/cve/CVE-2009-0357
suse.com/security/cve/CVE-2009-0358
suse.com/security/cve/CVE-2017-16541
suse.com/security/cve/CVE-2017-5373
suse.com/security/cve/CVE-2017-5374
suse.com/security/cve/CVE-2017-5375
suse.com/security/cve/CVE-2017-5376
suse.com/security/cve/CVE-2017-5377
suse.com/security/cve/CVE-2017-5378
suse.com/security/cve/CVE-2017-5379
suse.com/security/cve/CVE-2017-5380
suse.com/security/cve/CVE-2017-5381
suse.com/security/cve/CVE-2017-5382
suse.com/security/cve/CVE-2017-5383
suse.com/security/cve/CVE-2017-5384
suse.com/security/cve/CVE-2017-5385
suse.com/security/cve/CVE-2017-5386
suse.com/security/cve/CVE-2017-5387
suse.com/security/cve/CVE-2017-5388
suse.com/security/cve/CVE-2017-5389
suse.com/security/cve/CVE-2017-5390
suse.com/security/cve/CVE-2017-5391
suse.com/security/cve/CVE-2017-5392
suse.com/security/cve/CVE-2017-5393
suse.com/security/cve/CVE-2017-5394
suse.com/security/cve/CVE-2017-5395
suse.com/security/cve/CVE-2017-5396
suse.com/security/cve/CVE-2017-5398
suse.com/security/cve/CVE-2017-5399
suse.com/security/cve/CVE-2017-5400
suse.com/security/cve/CVE-2017-5401
suse.com/security/cve/CVE-2017-5402
suse.com/security/cve/CVE-2017-5403
suse.com/security/cve/CVE-2017-5404
suse.com/security/cve/CVE-2017-5405
suse.com/security/cve/CVE-2017-5406
suse.com/security/cve/CVE-2017-5407
suse.com/security/cve/CVE-2017-5408
suse.com/security/cve/CVE-2017-5410
suse.com/security/cve/CVE-2017-5412
suse.com/security/cve/CVE-2017-5413
suse.com/security/cve/CVE-2017-5414
suse.com/security/cve/CVE-2017-5415
suse.com/security/cve/CVE-2017-5416
suse.com/security/cve/CVE-2017-5417
suse.com/security/cve/CVE-2017-5418
suse.com/security/cve/CVE-2017-5419
suse.com/security/cve/CVE-2017-5420
suse.com/security/cve/CVE-2017-5421
suse.com/security/cve/CVE-2017-5422
suse.com/security/cve/CVE-2017-5426
suse.com/security/cve/CVE-2017-5427
suse.com/security/cve/CVE-2017-5428
suse.com/security/cve/CVE-2017-5429
suse.com/security/cve/CVE-2017-5430
suse.com/security/cve/CVE-2017-5432
suse.com/security/cve/CVE-2017-5433
suse.com/security/cve/CVE-2017-5434
suse.com/security/cve/CVE-2017-5435
suse.com/security/cve/CVE-2017-5436
suse.com/security/cve/CVE-2017-5437
suse.com/security/cve/CVE-2017-5438
suse.com/security/cve/CVE-2017-5439
suse.com/security/cve/CVE-2017-5440
suse.com/security/cve/CVE-2017-5441
suse.com/security/cve/CVE-2017-5442
suse.com/security/cve/CVE-2017-5443
suse.com/security/cve/CVE-2017-5444
suse.com/security/cve/CVE-2017-5445
suse.com/security/cve/CVE-2017-5446
suse.com/security/cve/CVE-2017-5447
suse.com/security/cve/CVE-2017-5448
suse.com/security/cve/CVE-2017-5449
suse.com/security/cve/CVE-2017-5451
suse.com/security/cve/CVE-2017-5453
suse.com/security/cve/CVE-2017-5454
suse.com/security/cve/CVE-2017-5455
suse.com/security/cve/CVE-2017-5456
suse.com/security/cve/CVE-2017-5458
suse.com/security/cve/CVE-2017-5459
suse.com/security/cve/CVE-2017-5460
suse.com/security/cve/CVE-2017-5461
suse.com/security/cve/CVE-2017-5462
suse.com/security/cve/CVE-2017-5464
suse.com/security/cve/CVE-2017-5465
suse.com/security/cve/CVE-2017-5466
suse.com/security/cve/CVE-2017-5467
suse.com/security/cve/CVE-2017-5468
suse.com/security/cve/CVE-2017-5469
suse.com/security/cve/CVE-2017-7753
suse.com/security/cve/CVE-2017-7779
suse.com/security/cve/CVE-2017-7780
suse.com/security/cve/CVE-2017-7781
suse.com/security/cve/CVE-2017-7782
suse.com/security/cve/CVE-2017-7783
suse.com/security/cve/CVE-2017-7784
suse.com/security/cve/CVE-2017-7785
suse.com/security/cve/CVE-2017-7786
suse.com/security/cve/CVE-2017-7787
suse.com/security/cve/CVE-2017-7788
suse.com/security/cve/CVE-2017-7789
suse.com/security/cve/CVE-2017-7790
suse.com/security/cve/CVE-2017-7791
suse.com/security/cve/CVE-2017-7792
suse.com/security/cve/CVE-2017-7793
suse.com/security/cve/CVE-2017-7794
suse.com/security/cve/CVE-2017-7796
suse.com/security/cve/CVE-2017-7797
suse.com/security/cve/CVE-2017-7798
suse.com/security/cve/CVE-2017-7799
suse.com/security/cve/CVE-2017-7800
suse.com/security/cve/CVE-2017-7801
suse.com/security/cve/CVE-2017-7802
suse.com/security/cve/CVE-2017-7803
suse.com/security/cve/CVE-2017-7804
suse.com/security/cve/CVE-2017-7805
suse.com/security/cve/CVE-2017-7806
suse.com/security/cve/CVE-2017-7807
suse.com/security/cve/CVE-2017-7808
suse.com/security/cve/CVE-2017-7809
suse.com/security/cve/CVE-2017-7810
suse.com/security/cve/CVE-2017-7811
suse.com/security/cve/CVE-2017-7812
suse.com/security/cve/CVE-2017-7813
suse.com/security/cve/CVE-2017-7814
lists.opensuse.org/archives/list/[email protected]/thread/3HI2RC7AJAHY74Q6MK7GNGWU6TITB22V
Left out here: 1,698 references and the rest of 1 source description. The JSON record has them.