p PatchFirst

PatchFirst · Latest vulnerabilities

mozjs52 vulnerabilities · Page 83

Vulnerabilities published for mozjs52 in the last 30 days: 257. Listed in the KEV catalogue: 0.

Filter vulnerabilities
Clear filters

Vulnerabilities: 1726

  1. CVE-2019-11709

    Critical · CVSS 9.8EPSS 2.35%No fix published

    CVE-2019-11709

    Mozilla developers and community members reported memory safety bugs present in Firefox 67 and Firefox ESR 60.7. Some of these bugs showed evidence of memory corruption and we presume that with enough effort that some of these could be exploited to run arbitrary code. This vulnerability affects Firefox ESR < 60.8, Firefox < 68, and Thunderbird < 60.8.

    Published Updated
  2. CVE-2019-11711

    High · CVSS 8.8EPSS 1.63%No fix published

    CVE-2019-11711

    When an inner window is reused, it does not consider the use of document.domain for cross-origin protections. If pages on different subdomains ever cooperatively use document.domain, then either page can abuse this to inject script into arbitrary pages on the other subdomain, even those that did not use document.domain to relax their origin security. This vulnerability affects Firefox ESR < 60.8, Firefox < 68, and Thunderbird < 60.8.

    Published Updated
  3. CVE-2019-11716

    High · CVSS 8.3EPSS 1.35%No fix published

    CVE-2019-11716

    Until explicitly accessed by script, window.globalThis is not enumerable and, as a result, is not visible to code such as Object.getOwnPropertyNames(window). Sites that deploy a sandboxing that depends on enumerating and freezing access to the window object may miss this, allowing their sandboxes to be bypassed. This vulnerability affects Firefox < 68.

    Published Updated
  4. CVE-2019-11718

    Medium · CVSS 5.3EPSS 1.23%No fix published

    CVE-2019-11718

    Activity Stream can display content from sent from the Snippet Service website. This content is written to innerHTML on the Activity Stream page without sanitization, allowing for a potential access to other information available to the Activity Stream, such as browsing history, if the Snipper Service were compromised. This vulnerability affects Firefox < 68.

    Published Updated
  5. CVE-2019-11719

    High · CVSS 7.5EPSS 2.29%No fix published

    CVE-2019-11719

    When importing a curve25519 private key in PKCS#8format with leading 0x00 bytes, it is possible to trigger an out-of-bounds read in the Network Security Services (NSS) library. This could lead to information disclosure. This vulnerability affects Firefox ESR < 60.8, Firefox < 68, and Thunderbird < 60.8.

    Published Updated
  6. CVE-2019-11723

    High · CVSS 7.5EPSS 0.81%No fix published

    CVE-2019-11723

    A vulnerability exists during the installation of add-ons where the initial fetch ignored the origin attributes of the browsing context. This could leak cookies in private browsing mode or across different "containers" for people who use the Firefox Multi-Account Containers Web Extension. This vulnerability affects Firefox < 68.

    Published Updated
  7. CVE-2019-11725

    Medium · CVSS 6.5EPSS 1.15%No fix published

    CVE-2019-11725

    When a user navigates to site marked as unsafe by the Safebrowsing API, warning messages are displayed and navigation is interrupted but resources from the same site loaded through websockets are not blocked, leading to the loading of unsafe resources and bypassing safebrowsing protections. This vulnerability affects Firefox < 68.

    Published Updated
  8. CVE-2019-11727

    Medium · CVSS 5.3EPSS 1.81%No fix published

    CVE-2019-11727

    A vulnerability exists where it possible to force Network Security Services (NSS) to sign CertificateVerify with PKCS#1 v1.5 signatures when those are the only ones advertised by server in CertificateRequest in TLS 1.3. PKCS#1 v1.5 signatures should not be used for TLS 1.3 messages. This vulnerability affects Firefox < 68.

    Published Updated
  9. CVE-2019-11730

    Medium · CVSS 6.5EPSS 20.27%No fix published

    CVE-2019-11730

    A vulnerability exists where if a user opens a locally saved HTML file, this file can use file: URIs to access other files in the same directory or sub-directories if the names are known or guessed. The Fetch API can then be used to read the contents of any files stored in these directories and they may uploaded to a server. It was demonstrated that in combination with a popular Android messaging app, if a malicious HTML attachment is sent to a user and they opened that attachment in Firefox, due to that app's predictable pattern for locally-saved file names, it is possible to read attachments the victim received from other correspondents. Th

    Published Updated

Check your server

Check your installed stack and versions against the current vulnerability feeds.

Check your server →