p PatchFirst

PatchFirst · Latest vulnerabilities

mozjs52 vulnerabilities · Page 77

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

Filter vulnerabilities
Clear filters

Vulnerabilities: 1727

  1. CVE-2020-12410

    High · CVSS 8.8EPSS 1.73%No fix published

    CVE-2020-12410

    Mozilla developers reported memory safety bugs present in Firefox 76 and Firefox ESR 68.8. Some of these bugs showed evidence of memory corruption and we presume that with enough effort some of these could have been exploited to run arbitrary code. This vulnerability affects Thunderbird < 68.9.0, Firefox < 77, and Firefox ESR < 68.9.

    Published Updated
  2. CVE-2020-12421

    Medium · CVSS 6.5EPSS 1.84%No fix published

    CVE-2020-12421

    When performing add-on updates, certificate chains terminating in non-built-in-roots were rejected (even if they were legitimately added by an administrator.) This could have caused add-ons to become out-of-date silently without notification to the user. This vulnerability affects Firefox ESR < 68.10, Firefox < 78, and Thunderbird < 68.10.0.

    Published Updated
  3. CVE-2020-12419

    High · CVSS 8.8EPSS 2.32%No fix published

    CVE-2020-12419

    When processing callbacks that occurred during window flushing in the parent process, the associated window may die; causing a use-after-free condition. This could have led to memory corruption and a potentially exploitable crash. This vulnerability affects Firefox ESR < 68.10, Firefox < 78, and Thunderbird < 68.10.0.

    Published Updated
  4. CVE-2020-12417

    High · CVSS 8.8EPSS 2.68%No fix published

    CVE-2020-12417

    Due to confusion about ValueTags on JavaScript Objects, an object may pass through the type barrier, resulting in memory corruption and a potentially exploitable crash. *Note: this issue only affects Firefox on ARM64 platforms.* This vulnerability affects Firefox ESR < 68.10, Firefox < 78, and Thunderbird < 68.10.0.

    Published Updated

Check your server

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

Check your server →