p PatchFirst

PatchFirst · Aktuelle Sicherheitslücken

Sicherheitslücken in enigmail

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

Sicherheitslücken filtern
Filter zurücksetzen

Sicherheitslücken: 15

  1. CVE-2019-14664

    Mittel · CVSS 6.5EPSS 1,03%Korrektur verfügbar

    CVE-2019-14664

    In Enigmail below 2.1, an attacker in possession of PGP encrypted emails can wrap them as sub-parts within a crafted multipart email. The encrypted part(s) can further be hidden using HTML/CSS or ASCII newline characters. This modified multipart email can be re-sent by the attacker to the intended receiver. If the receiver replies to this (benign looking) email, he unknowingly leaks the plaintext of the encrypted message part(s) back to the attacker. This attack variant bypasses protection mechanisms implemented after the "EFAIL" attacks.

    • Auf 2:2.1.3+ds1-1 aktualisieren
    Veröffentlicht Aktualisiert
  2. CVE-2018-12019

    Hoch · CVSS 7.5EPSS 2,06%Korrektur verfügbar

    CVE-2018-12019

    The signature verification routine in Enigmail before 2.0.7 interprets user ids as status/control messages and does not correctly keep track of the status of multiple signatures, which allows remote attackers to spoof arbitrary email signatures via public keys containing crafted primary user ids.

    • Auf 2:2.0.7-1 aktualisieren
    Veröffentlicht Aktualisiert
  3. CVE-2017-17688

    Mittel · CVSS 5.9EPSS 5,44%Korrektur verfügbar

    CVE-2017-17688

    The OpenPGP specification allows a Cipher Feedback Mode (CFB) malleability-gadget attack that can indirectly lead to plaintext exfiltration, aka EFAIL. NOTE: third parties report that this is a problem in applications that mishandle the Modification Detection Code (MDC) feature or accept an obsolete packet type, not a problem in the OpenPGP specification

    • Auf 2:2.0.6.1-4 aktualisieren
    Veröffentlicht Aktualisiert
  4. CVE-2017-17848

    Hoch · CVSS 7.5EPSS 1,84%Korrektur verfügbar

    CVE-2017-17848

    An issue was discovered in Enigmail before 1.9.9. In a variant of CVE-2017-17847, signature spoofing is possible for multipart/related messages because a signed message part can be referenced with a cid: URI but not actually displayed. In other words, the entire containing message appears to be signed, but the recipient does not see any of the signed text.

    • Auf 2:1.9.9-1 aktualisieren
    Veröffentlicht Aktualisiert
  5. CVE-2017-17847

    Hoch · CVSS 7.5EPSS 1,2%Korrektur verfügbar

    CVE-2017-17847

    An issue was discovered in Enigmail before 1.9.9. Signature spoofing is possible because the UI does not properly distinguish between an attachment signature, and a signature that applies to the entire containing message, aka TBE-01-021. This is demonstrated by an e-mail message with an attachment that is a signed e-mail message in message/rfc822 format.

    • Auf 2:1.9.9-1 aktualisieren
    Veröffentlicht Aktualisiert
  6. CVE-2017-17844

    Mittel · CVSS 6.5EPSS 1,35%Korrektur verfügbar

    CVE-2017-17844

    An issue was discovered in Enigmail before 1.9.9. A remote attacker can obtain cleartext content by sending an encrypted data block (that the attacker cannot directly decrypt) to a victim, and relying on the victim to automatically decrypt that block and then send it back to the attacker as quoted text, aka the TBE-01-005 "replay" issue.

    • Auf 2:1.9.9-1 aktualisieren
    Veröffentlicht Aktualisiert
  7. CVE-2017-17843

    Mittel · CVSS 5.9EPSS 1,12%Korrektur verfügbar

    CVE-2017-17843

    An issue was discovered in Enigmail before 1.9.9 that allows remote attackers to trigger use of an intended public key for encryption, because incorrect regular expressions are used for extraction of an e-mail address from a comma-separated list, as demonstrated by a modified Full Name field and a homograph attack, aka TBE-01-002.

    • Auf 2:1.9.9-1 aktualisieren
    Veröffentlicht Aktualisiert
  8. CVE-2007-1264

    Nicht bewertetEPSS 4,75%Öffentlicher ExploitKorrektur verfügbar

    CVE-2007-1264

    Enigmail 0.94.2 and earlier does not properly use the --status-fd argument when invoking GnuPG, which prevents Enigmail from visually distinguishing between signed and unsigned portions of OpenPGP messages with multiple components, which allows remote attackers to forge the contents of a message without detection.

    • Auf 2:0.95.0+1-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 →