p PatchFirst

PatchFirst · Aktuelle Sicherheitslücken

Sicherheitslücken in pidgin

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

Sicherheitslücken filtern
Filter zurücksetzen

Sicherheitslücken: 82

  1. CVE-2022-26491

    Mittel · CVSS 5.9EPSS 2,56%Korrektur verfügbar

    CVE-2022-26491

    An issue was discovered in Pidgin before 2.14.9. A remote attacker who can spoof DNS responses can redirect a client connection to a malicious server. The client will perform TLS certificate verification of the malicious domain name instead of the original XMPP service domain, allowing the attacker to take over control over the XMPP connection and to obtain user credentials and all communication content. This is similar to CVE-2022-24968.

    • Auf 2.14.9-1 aktualisieren
    Veröffentlicht Aktualisiert
  2. CVE-2016-1000030

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

    CVE-2016-1000030

    Pidgin version <2.11.0 contains a vulnerability in X.509 Certificates imports specifically due to improper check of return values from gnutls_x509_crt_init() and gnutls_x509_crt_import() that can result in code execution. This attack appear to be exploitable via custom X.509 certificate from another client. This vulnerability appears to have been fixed in 2.11.0.

    • Auf 2.11.0-1 aktualisieren
    Veröffentlicht Aktualisiert
  3. CVE-2016-4323

    Niedrig · CVSS 3.7EPSS 2,3%Korrektur verfügbar

    CVE-2016-4323

    A directory traversal exists in the handling of the MXIT protocol in Pidgin. Specially crafted MXIT data sent from the server could potentially result in an overwrite of files. A malicious server or someone with access to the network traffic can provide an invalid filename for a splash image triggering the vulnerability.

    • Auf 2.11.0-1 aktualisieren
    Veröffentlicht Aktualisiert
  4. CVE-2016-2380

    Niedrig · CVSS 3.1EPSS 1,75%Korrektur verfügbar

    CVE-2016-2380

    An information leak exists in the handling of the MXIT protocol in Pidgin. Specially crafted MXIT data sent to the server could potentially result in an out-of-bounds read. A user could be convinced to enter a particular string which would then get converted incorrectly and could lead to a potential out-of-bounds read.

    • Auf 2.11.0-1 aktualisieren
    Veröffentlicht Aktualisiert
  5. CVE-2016-2378

    Hoch · CVSS 8.1EPSS 2,5%Korrektur verfügbar

    CVE-2016-2378

    A buffer overflow vulnerability exists in the handling of the MXIT protocol Pidgin. Specially crafted data sent via the server could potentially result in a buffer overflow, potentially resulting in memory corruption. A malicious server or an unfiltered malicious user can send negative length values to trigger this vulnerability.

    • Auf 2.11.0-1 aktualisieren
    Veröffentlicht Aktualisiert
  6. CVE-2016-2377

    Hoch · CVSS 8.1EPSS 2,61%Korrektur verfügbar

    CVE-2016-2377

    A buffer overflow vulnerability exists in the handling of the MXIT protocol in Pidgin. Specially crafted MXIT data sent by the server could potentially result in an out-of-bounds write of one byte. A malicious server can send a negative content-length in response to a HTTP request triggering the vulnerability.

    • Auf 2.11.0-1 aktualisieren
    Veröffentlicht Aktualisiert
  7. CVE-2016-2376

    Hoch · CVSS 8.1EPSS 3,72%Korrektur verfügbar

    CVE-2016-2376

    A buffer overflow vulnerability exists in the handling of the MXIT protocol in Pidgin. Specially crafted MXIT data sent from the server could potentially result in arbitrary code execution. A malicious server or an attacker who intercepts the network traffic can send an invalid size for a packet which will trigger a buffer overflow.

    • Auf 2.11.0-1 aktualisieren
    Veröffentlicht Aktualisiert
  8. CVE-2016-2374

    Hoch · CVSS 8.1EPSS 3,22%Korrektur verfügbar

    CVE-2016-2374

    An exploitable memory corruption vulnerability exists in the handling of the MXIT protocol in Pidgin. Specially crafted MXIT MultiMX message sent via the server can result in an out-of-bounds write leading to memory disclosure and code execution.

    • Auf 2.11.0-1 aktualisieren
    Veröffentlicht Aktualisiert
  9. CVE-2016-2373

    Mittel · CVSS 5.9EPSS 2,29%Korrektur verfügbar

    CVE-2016-2373

    A denial of service vulnerability exists in the handling of the MXIT protocol in Pidgin. Specially crafted MXIT data sent via the server could potentially result in an out-of-bounds read. A malicious server or user can send an invalid mood to trigger this vulnerability.

    • Auf 2.11.0-1 aktualisieren
    Veröffentlicht Aktualisiert
  10. CVE-2016-2372

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

    CVE-2016-2372

    An information leak exists in the handling of the MXIT protocol in Pidgin. Specially crafted MXIT data sent via the server could potentially result in an out-of-bounds read. A malicious user, server, or man-in-the-middle attacker can send an invalid size for a file transfer which will trigger an out-of-bounds read vulnerability. This could result in a denial of service or copy data from memory to the file, resulting in an information leak if the file is sent to another user.

    • Auf 2.11.0-1 aktualisieren
    Veröffentlicht Aktualisiert
  11. CVE-2016-2370

    Mittel · CVSS 5.9EPSS 2,11%Korrektur verfügbar

    CVE-2016-2370

    A denial of service vulnerability exists in the handling of the MXIT protocol in Pidgin. Specially crafted MXIT data sent from the server could potentially result in an out-of-bounds read. A malicious server or man-in-the-middle attacker can send invalid data to trigger this vulnerability.

    • Auf 2.11.0-1 aktualisieren
    Veröffentlicht Aktualisiert
  12. CVE-2016-2369

    Mittel · CVSS 5.9EPSS 2,23%Korrektur verfügbar

    CVE-2016-2369

    A NULL pointer dereference vulnerability exists in the handling of the MXIT protocol in Pidgin. Specially crafted MXIT data sent via the server could potentially result in a denial of service vulnerability. A malicious server can send a packet starting with a NULL byte triggering the vulnerability.

    • Auf 2.11.0-1 aktualisieren
    Veröffentlicht Aktualisiert
  13. CVE-2016-2368

    Hoch · CVSS 8.1EPSS 4,64%Korrektur verfügbar

    CVE-2016-2368

    Multiple memory corruption vulnerabilities exist in the handling of the MXIT protocol in Pidgin. Specially crafted MXIT data sent via the server could result in multiple buffer overflows, potentially resulting in code execution or memory disclosure.

    • Auf 2.11.0-1 aktualisieren
    Veröffentlicht Aktualisiert
  14. CVE-2016-2367

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

    CVE-2016-2367

    An information leak exists in the handling of the MXIT protocol in Pidgin. Specially crafted MXIT data sent via the server could potentially result in an out-of-bounds read. A malicious user, server, or man-in-the-middle can send an invalid size for an avatar which will trigger an out-of-bounds read vulnerability. This could result in a denial of service or copy data from memory to the file, resulting in an information leak if the avatar is sent to another user.

    • Auf 2.11.0-1 aktualisieren
    Veröffentlicht Aktualisiert
  15. CVE-2016-2366

    Mittel · CVSS 5.9EPSS 2,47%Korrektur verfügbar

    CVE-2016-2366

    A denial of service vulnerability exists in the handling of the MXIT protocol in Pidgin. Specially crafted MXIT data sent via the server could potentially result in an out-of-bounds read. A malicious server or an attacker who intercepts the network traffic can send invalid data to trigger this vulnerability and cause a crash.

    • Auf 2.11.0-1 aktualisieren
    Veröffentlicht Aktualisiert
  16. CVE-2016-2365

    Mittel · CVSS 5.9EPSS 2,41%Korrektur verfügbar

    CVE-2016-2365

    A denial of service vulnerability exists in the handling of the MXIT protocol in Pidgin. Specially crafted MXIT data sent via the server could potentially result in a null pointer dereference. A malicious server or an attacker who intercepts the network traffic can send invalid data to trigger this vulnerability and cause a crash.

    • Auf 2.11.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 →