p PatchFirst

PatchFirst · Aktuelle Sicherheitslücken

Sicherheitslücken in thunderbird · Seite 47

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

Sicherheitslücken filtern
Filter zurücksetzen

Sicherheitslücken: 1318

  1. CVE-2022-3033

    Hoch · CVSS 8.1EPSS 0,8%Korrektur verfügbar

    CVE-2022-3033

    If a Thunderbird user replied to a crafted HTML email containing a <code>meta</code> tag, with the <code>meta</code> tag having the <code>http-equiv="refresh"</code> attribute, and the content attribute specifying an URL, then Thunderbird started a network request to that URL, regardless of the configuration to block remote content. In combination with certain other HTML elements and attributes in the email, it was possible to execute JavaScript code included in the message in the context of the message compose document. The JavaScript code was able to perform actions including, but probably not limited to, read and modify the contents of the

    • Auf 1:102.2.1-1 aktualisieren
    Veröffentlicht Aktualisiert
  2. CVE-2022-3032

    Mittel · CVSS 6.5EPSS 0,71%Korrektur verfügbar

    CVE-2022-3032

    When receiving an HTML email that contained an <code>iframe</code> element, which used a <code>srcdoc</code> attribute to define the inner HTML document, remote objects specified in the nested document, for example images or videos, were not blocked. Rather, the network was accessed, the objects were loaded and displayed. This vulnerability affects Thunderbird < 102.2.1 and Thunderbird < 91.13.1.

    • Auf 1:102.2.1-1 aktualisieren
    Veröffentlicht Aktualisiert
  3. CVE-2022-29917

    Kritisch · CVSS 9.8EPSS 1,05%Korrektur verfügbar

    CVE-2022-29917

    Mozilla developers Andrew McCreight, Gabriele Svelto, Tom Ritter and the Mozilla Fuzzing Team reported memory safety bugs present in Firefox 99 and Firefox ESR 91.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 < 91.9, Firefox ESR < 91.9, and Firefox < 100.

    • Auf 1:91.9.0-1 aktualisieren
    Veröffentlicht Aktualisiert
  4. CVE-2022-29916

    Mittel · CVSS 6.5EPSS 0,76%Korrektur verfügbar

    CVE-2022-29916

    Firefox behaved slightly differently for already known resources when loading CSS resources involving CSS variables. This could have been used to probe the browser history. This vulnerability affects Thunderbird < 91.9, Firefox ESR < 91.9, and Firefox < 100.

    • Auf 1:91.9.0-1 aktualisieren
    Veröffentlicht Aktualisiert
  5. CVE-2022-29911

    Mittel · CVSS 6.1EPSS 0,61%Korrektur verfügbar

    CVE-2022-29911

    An improper implementation of the new iframe sandbox keyword <code>allow-top-navigation-by-user-activation</code> could lead to script execution without <code>allow-scripts</code> being present. This vulnerability affects Thunderbird < 91.9, Firefox ESR < 91.9, and Firefox < 100.

    • Auf 1:91.9.0-1 aktualisieren
    Veröffentlicht Aktualisiert
  6. CVE-2022-29909

    Hoch · CVSS 8.8EPSS 0,89%Korrektur verfügbar

    CVE-2022-29909

    Documents in deeply-nested cross-origin browsing contexts could have obtained permissions granted to the top-level origin, bypassing the existing prompt and wrongfully inheriting the top-level permissions. This vulnerability affects Thunderbird < 91.9, Firefox ESR < 91.9, and Firefox < 100.

    • Auf 1:91.9.0-1 aktualisieren
    Veröffentlicht Aktualisiert
  7. CVE-2022-28289

    Hoch · CVSS 8.8EPSS 0,74%Korrektur verfügbar

    CVE-2022-28289

    Mozilla developers and community members Nika Layzell, Andrew McCreight, Gabriele Svelto, and the Mozilla Fuzzing Team reported memory safety bugs present in Thunderbird 91.7. 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 < 91.8, Firefox < 99, and Firefox ESR < 91.8.

    • Auf 1:91.8.0-1 aktualisieren
    Veröffentlicht Aktualisiert
  8. CVE-2022-28285

    Mittel · CVSS 6.5EPSS 0,79%Korrektur verfügbar

    CVE-2022-28285

    When generating the assembly code for <code>MLoadTypedArrayElementHole</code>, an incorrect AliasSet was used. In conjunction with another vulnerability this could have been used for an out of bounds memory read. This vulnerability affects Thunderbird < 91.8, Firefox < 99, and Firefox ESR < 91.8.

    • Auf 1:91.8.0-1 aktualisieren
    Veröffentlicht Aktualisiert
  9. CVE-2022-28282

    Mittel · CVSS 6.5EPSS 2,18%Korrektur verfügbar

    CVE-2022-28282

    By using a link with <code>rel="localization"</code> a use-after-free could have been triggered by destroying an object during JavaScript execution and then referencing the object through a freed pointer, leading to a potential exploitable crash. This vulnerability affects Thunderbird < 91.8, Firefox < 99, and Firefox ESR < 91.8.

    • Auf 1:91.8.0-1 aktualisieren
    Veröffentlicht Aktualisiert
  10. CVE-2022-28281

    Hoch · CVSS 8.8EPSS 2,78%Korrektur verfügbar

    CVE-2022-28281

    If a compromised content process sent an unexpected number of WebAuthN Extensions in a Register command to the parent process, an out of bounds write would have occurred leading to memory corruption and a potentially exploitable crash. This vulnerability affects Thunderbird < 91.8, Firefox < 99, and Firefox ESR < 91.8.

    • Auf 1:91.8.0-1 aktualisieren
    Veröffentlicht Aktualisiert
  11. CVE-2022-26486

    Kritisch · CVSS 9.6EPSS 2,36%Im KEV-KatalogKorrektur verfügbar

    CVE-2022-26486

    An unexpected message in the WebGPU IPC framework could lead to a use-after-free and exploitable sandbox escape. We have had reports of attacks in the wild abusing this flaw. This vulnerability affects Firefox < 97.0.2, Firefox ESR < 91.6.1, Firefox for Android < 97.3.0, Thunderbird < 91.6.2, and Focus < 97.3.0.

    • Auf 1:91.6.2-1 aktualisieren
    Veröffentlicht Aktualisiert
  12. CVE-2022-26485

    Hoch · CVSS 8.8EPSS 14,26%Im KEV-KatalogKorrektur verfügbar

    CVE-2022-26485

    Removing an XSLT parameter during processing could have lead to an exploitable use-after-free. We have had reports of attacks in the wild abusing this flaw. This vulnerability affects Firefox < 97.0.2, Firefox ESR < 91.6.1, Firefox for Android < 97.3.0, Thunderbird < 91.6.2, and Focus < 97.3.0.

    • Auf 1:91.6.2-1 aktualisieren
    Veröffentlicht Aktualisiert
  13. CVE-2022-26387

    Hoch · CVSS 7.5EPSS 0,66%Korrektur verfügbar

    CVE-2022-26387

    When installing an add-on, Firefox verified the signature before prompting the user; but while the user was confirming the prompt, the underlying add-on file could have been modified and Firefox would not have noticed. This vulnerability affects Firefox < 98, Firefox ESR < 91.7, and Thunderbird < 91.7.

    • Auf 1:91.7.0-1 aktualisieren
    Veröffentlicht Aktualisiert
  14. CVE-2022-26386

    Mittel · CVSS 6.5EPSS 0,71%Korrektur verfügbar

    CVE-2022-26386

    Previously Firefox for macOS and Linux would download temporary files to a user-specific directory in <code>/tmp</code>, but this behavior was changed to download them to <code>/tmp</code> where they could be affected by other local users. This behavior was reverted to the original, user-specific directory. <br>*This bug only affects Firefox for macOS and Linux. Other operating systems are unaffected.*. This vulnerability affects Firefox ESR < 91.7 and Thunderbird < 91.7.

    • Auf 1:91.7.0-1 aktualisieren
    Veröffentlicht Aktualisiert
  15. CVE-2022-26384

    Kritisch · CVSS 9.6EPSS 0,97%Korrektur verfügbar

    CVE-2022-26384

    If an attacker could control the contents of an iframe sandboxed with <code>allow-popups</code> but not <code>allow-scripts</code>, they were able to craft a link that, when clicked, would lead to JavaScript execution in violation of the sandbox. This vulnerability affects Firefox < 98, Firefox ESR < 91.7, and Thunderbird < 91.7.

    • Auf 1:91.7.0-1 aktualisieren
    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 →