LiveActive security incident?Get immediate response
CVE Record

CVE-2017-5384: Proxy Auto-Config (PAC) files can specify a JavaScript function called for all URL requests with the full U...

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

Older Firefox versions could reveal full HTTPS URL paths to Proxy Auto-Config logic. That matters because paths can contain sensitive business data, tokens, document names, or internal application context. The risk is most relevant where Firefox before version 51 remains in use and WPAD or remotely supplied PAC files are enabled. Exposure is likely limited to legacy Firefox installations below version 51, especially managed desktops using WPAD or PAC-based proxy configuration. Current Firefox versions are outside the stated affected range. The bundle does not identify other Mozilla products or non-Mozilla browsers as affected. Prioritize remediation if legacy Firefox and WPAD are still present. The business risk is sensitive URL leakage, which can expose internal activity and application context. If the estate has already removed Firefox below 51, residual urgency is low. Mitigation focus: Upgrade Firefox to version 51 or later.; Disable WPAD where it is not operationally required.; Ensure PAC files come only from trusted, controlled infrastructure..

Prepared

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2017-5384 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
MozillaFirefoxunspecifiedListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.