p PatchFirst

PatchFirst · Aktuelle Sicherheitslücken

Sicherheitslücken in mozjs78 · Seite 74

In den letzten 30 Tagen veröffentlichte Sicherheitslücken für mozjs78: 257. Davon im KEV-Katalog: 0.

Sicherheitslücken filtern
Filter zurücksetzen

Sicherheitslücken: 1468

  1. CVE-2020-26974

    Hoch · CVSS 8.8EPSS 1,53%Keine Korrektur veröffentlicht

    CVE-2020-26974

    When flex-basis was used on a table wrapper, a StyleGenericFlexBasis object could have been incorrectly cast to the wrong type. This resulted in a heap user-after-free, memory corruption, and a potentially exploitable crash. This vulnerability affects Firefox < 84, Thunderbird < 78.6, and Firefox ESR < 78.6.

    Veröffentlicht Aktualisiert
  2. CVE-2020-26976

    Mittel · CVSS 6.5EPSS 1,64%Keine Korrektur veröffentlicht

    CVE-2020-26976

    When a HTTPS pages was embedded in a HTTP page, and there was a service worker registered for the former, the service worker could have intercepted the request for the secure page despite the iframe not being a secure context due to the (insecure) framing. This vulnerability affects Firefox < 84.

    Veröffentlicht Aktualisiert
  3. CVE-2020-26978

    Mittel · CVSS 6.1EPSS 1,33%Keine Korrektur veröffentlicht

    CVE-2020-26978

    Using techniques that built on the slipstream research, a malicious webpage could have exposed both an internal network's hosts as well as services running on the user's local machine. This vulnerability affects Firefox < 84, Thunderbird < 78.6, and Firefox ESR < 78.6.

    Veröffentlicht Aktualisiert
  4. CVE-2020-26979

    Mittel · CVSS 6.1EPSS 0,73%Keine Korrektur veröffentlicht

    CVE-2020-26979

    When a user typed a URL in the address bar or the search bar and quickly hit the enter key, a website could sometimes capture that event and then redirect the user before navigation occurred to the desired, entered address. To construct a convincing spoof the attacker would have had to guess what the user was typing, perhaps by suggesting it. This vulnerability affects Firefox < 84.

    Veröffentlicht Aktualisiert
  5. CVE-2020-35111

    Mittel · CVSS 4.3EPSS 1,43%Keine Korrektur veröffentlicht

    CVE-2020-35111

    When an extension with the proxy permission registered to receive <all_urls>, the proxy.onRequest callback was not triggered for view-source URLs. While web content cannot navigate to such URLs, a user opening View Source could have inadvertently leaked their IP address. This vulnerability affects Firefox < 84, Thunderbird < 78.6, and Firefox ESR < 78.6.

    Veröffentlicht Aktualisiert
  6. CVE-2020-35112

    Hoch · CVSS 8.8EPSS 1,27%Keine Korrektur veröffentlicht

    CVE-2020-35112

    If a user downloaded a file lacking an extension on Windows, and then "Open"-ed it from the downloads panel, if there was an executable file in the downloads directory with the same name but with an executable extension (such as .bat or .exe) that executable would have been launched instead. *Note: This issue only affected Windows operating systems. Other operating systems are unaffected.*. This vulnerability affects Firefox < 84, Thunderbird < 78.6, and Firefox ESR < 78.6.

    Veröffentlicht Aktualisiert
  7. CVE-2020-35113

    Hoch · CVSS 8.8EPSS 1,57%Keine Korrektur veröffentlicht

    CVE-2020-35113

    Mozilla developers reported memory safety bugs present in Firefox 83 and Firefox ESR 78.5. 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 Firefox < 84, Thunderbird < 78.6, and Firefox ESR < 78.6.

    Veröffentlicht Aktualisiert
  8. CVE-2020-35114

    Hoch · CVSS 8.8EPSS 1,05%Keine Korrektur veröffentlicht

    CVE-2020-35114

    Mozilla developers reported memory safety bugs present in Firefox 83. 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 Firefox < 84.

    Veröffentlicht Aktualisiert

Prüfen Sie Ihren Server

Gleichen Sie Ihren installierten Stack und seine Versionen mit den aktuellen Sicherheitsmeldungen ab.

Prüfen Sie Ihren Server →