p PatchFirst

PatchFirst · Aktuelle Sicherheitslücken

Sicherheitslücken in wolfssl · Seite 6

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

Sicherheitslücken filtern
Filter zurücksetzen

Sicherheitslücken: 112

  1. CVE-2022-39173

    Hoch · CVSS 7.5EPSS 5,76%Keine Korrektur veröffentlicht

    CVE-2022-39173

    In wolfSSL before 5.5.1, malicious clients can cause a buffer overflow during a TLS 1.3 handshake. This occurs when an attacker supposedly resumes a previous TLS session. During the resumption Client Hello a Hello Retry Request must be triggered. Both Client Hellos are required to contain a list of duplicate cipher suites to trigger the buffer overflow. In total, two Client Hellos have to be sent: one in the resumed session, and a second one as a response to a Hello Retry Request message.

    Veröffentlicht Aktualisiert
  2. CVE-2022-38153

    Mittel · CVSS 5.9EPSS 2,48%Keine Korrektur veröffentlicht

    CVE-2022-38153

    An issue was discovered in wolfSSL before 5.5.0 (when --enable-session-ticket is used); however, only version 5.3.0 is exploitable. Man-in-the-middle attackers or a malicious server can crash TLS 1.2 clients during a handshake. If an attacker injects a large ticket (more than 256 bytes) into a NewSessionTicket message in a TLS 1.2 handshake, and the client has a non-empty session cache, the session cache frees a pointer that points to unallocated memory, causing the client to crash with a "free(): invalid pointer" message. NOTE: It is likely that this is also exploitable during TLS 1.3 handshakes between a client and a malicious server. With

    Veröffentlicht Aktualisiert
  3. CVE-2022-38152

    Hoch · CVSS 7.5EPSS 2,92%Keine Korrektur veröffentlicht

    CVE-2022-38152

    An issue was discovered in wolfSSL before 5.5.0. When a TLS 1.3 client connects to a wolfSSL server and SSL_clear is called on its session, the server crashes with a segmentation fault. This occurs in the second session, which is created through TLS session resumption and reuses the initial struct WOLFSSL. If the server reuses the previous session structure (struct WOLFSSL) by calling wolfSSL_clear(WOLFSSL* ssl) on it, the next received Client Hello (that resumes the previous session) crashes the server. Note that this bug is only triggered when resuming sessions using TLS session resumption. Only servers that use wolfSSL_clear instead of the

    Veröffentlicht Aktualisiert
  4. CVE-2021-24116

    Mittel · CVSS 4.9EPSS 1,19%Keine Korrektur veröffentlicht

    CVE-2021-24116

    In wolfSSL through 4.6.0, a side-channel vulnerability in base64 PEM file decoding allows system-level (administrator) attackers to obtain information about secret RSA keys via a controlled-channel and side-channel attack on software running in isolated environments that can be single stepped, especially Intel SGX.

    Veröffentlicht Aktualisiert
  5. CVE-2021-3336

    Hoch · CVSS 8.1EPSS 0,8%Keine Korrektur veröffentlicht

    CVE-2021-3336

    DoTls13CertificateVerify in tls13.c in wolfSSL before 4.7.0 does not cease processing for certain anomalous peer behavior (sending an ED22519, ED448, ECC, or RSA signature without the corresponding certificate). The client side is affected because man-in-the-middle attackers can impersonate TLS 1.3 servers.

    Veröffentlicht Aktualisiert
  6. CVE-2018-12436

    Mittel · CVSS 4.7EPSS 0,38%Keine Korrektur veröffentlicht

    CVE-2018-12436

    wolfcrypt/src/ecc.c in wolfSSL before 3.15.1.patch allows a memory-cache side-channel attack on ECDSA signatures, aka the Return Of the Hidden Number Problem or ROHNP. To discover an ECDSA key, the attacker needs access to either the local machine or a different virtual machine on the same physical host.

    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 →