p PatchFirst

PatchFirst · Aktuelle Sicherheitslücken

openssl 4.0.2: bekannte Sicherheitslücken

Bekannte Sicherheitslücken für openssl 4.0.2: 14. Vergleichen Sie die unten genannten Korrekturen mit Ihrer installierten Version.

RSS ↗
Sicherheitslücken filtern
Filter zurücksetzen

Sicherheitslücken: 14

  1. CVE-2026-84784

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

    QUIC: Unbounded RETIRE_CONNECTION_ID Backlog

    Issue summary: A malicious remote peer may flood the local QUIC stack with NEW_CONNECTION_ID frames by avoiding a limit check on how many connection IDs the remote QUIC stack can use. Impact summary: The local QUIC stack sends a RETIRE_CONN_ID frame for every NEW_CONNECTION_ID frame it receives. The RETIRE_CONN_ID frame is dispatched via the Control Frame Queue (CFQ). If the remote peer also withholds ACKs, then it can force the local stack to allocate ~400MB (depending on ACK delay). CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: RFC 9000 sections 5.1.1 and 5.1.2 [1] describe the mechanism by which a remot

    • Auf 4.0.3 aktualisieren
    Veröffentlicht Aktualisiert
  2. CVE-2026-84783

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

    Use-After-Free in X.509 Extension Cache Under Concurrent Use

    Issue summary: The first concurrent use of the same X.509 certificate by several threads may cause its cached extension data to be freed while another thread is still using it. Impact summary: A remote, unauthenticated peer could crash a multi-threaded TLS client, or a multi-threaded TLS server that requests client certificates, if the first certificate chains built to the same trusted CA certificate are built by several connections at the same time. This is a use-after-free read, which is likely to crash the process, resulting in a Denial of Service. CWE: CWE-416: Use After Free Description: OpenSSL caches the decoded values of a certific

    • Auf 4.0.3 aktualisieren
    Veröffentlicht Aktualisiert
  3. CVE-2026-84782

    Hoch · CVSS 8.2EPSS 0,39%Korrektur verfügbar

    DTLS Retransmits Handshake Messages From a Stale Buffer Offset

    Issue summary: The DTLS retransmission logic does not correctly handle a handshake message write that is suspended part-way through. The retransmitted message can be read past the message buffer and the retransmission overwrites the internal state the suspended write needs to resume correctly. Impact summary: The retransmitted message can disclose a heap memory to the peer as plaintext handshake data or cause a crash and a Denial of Service when the read reaches an unmapped memory region. CWE: CWE-125: Out-of-bounds Read Description: DTLS handshake messages can be written out in multiple fragments, and a write can suspend mid-message (retu

    • Auf 4.0.3 aktualisieren
    Veröffentlicht Aktualisiert
  4. CVE-2026-77696

    Niedrig · CVSS 3.7EPSS 0,24%Korrektur verfügbar

    Timing Side-Channel in SM2 Signature Generation

    Issue summary: SM2 signature generation uses non-constant-time arithmetic on secret values, forming a timing side-channel. Impact summary: An attacker able to measure SM2 signing times may learn information about the per-signature secret nonce, which over many signatures can, via a lattice / Hidden Number Problem attack, lead to recovery of the private key. CWE: CWE-208: Observable Timing Discrepancy Description: SM2 signature generation computes the signature value using variable-time BIGNUM operations on the secret nonce and the private key, so the time taken to produce an SM2 signature depends on these secret values, forming a timing si

    • Auf 4.0.3 aktualisieren
    Veröffentlicht Aktualisiert
  5. CVE-2026-75806

    Mittel · CVSS 5.3EPSS 0,39%Korrektur verfügbar

    Unauthenticated and Undersized DTLS 1.2 AEAD Record Causes DoS

    Issue summary: An established DTLS 1.2 association using an AEAD cipher suite can be terminated by a single unauthenticated datagram whose encrypted fragment is shorter than the mandatory explicit IV and authentication tag overhead. Impact summary: An attacker who can send a datagram that is routed to an existing DTLS 1.2 association can tear that association down without knowing any key material. This is a Denial of Service limited to the targeted association. There is no memory safety or confidentiality impact. CWE: CWE-1284: Improper Validation of Specified Quantity in Input Description: In TLS 1.2 and DTLS 1.2 every record protected by

    • Auf 4.0.3 aktualisieren
    Veröffentlicht Aktualisiert
  6. CVE-2026-75805

    Mittel · CVSS 5.3EPSS 0,22%Korrektur verfügbar

    NULL Pointer Dereference in CMP Client Revocation Response Handling

    Issue summary: A CMP client that requests certificate revocation on the basis of a PKCS#10 CSR may dereference a NULL pointer and terminate abnormally when processing a crafted revocation response. Impact summary: The NULL pointer dereference happens on a read which leads to a crash and a Denial of Service for the affected client application. CWE: CWE-476: NULL-pointer dereference Description: A CMP client revoking a certificate has to tell the server which certificate to revoke, and may do so by supplying a PKCS#10 CSR instead of the certificate itself or its issuer name and serial number. This is 'openssl cmp -cmd rr -csr <file>' on th

    • Auf 4.0.3 aktualisieren
    Veröffentlicht Aktualisiert
  7. CVE-2026-75804

    Mittel · CVSS 5.3EPSS 0,35%Korrektur verfügbar

    QUIC Connection-Level Flow Control is Not Enforced for Streams

    Issue summary: OpenSSL QUIC stack does not enforce connection level flow control for streams. Remote peers may send more bytes as long as they fit within the stream flow control limits. Impact summary: A malicious remote peer may exploit the lack of connection flow control for streams to make the QUIC stack receive ~100MB of memory instead of 768 KiB (default flow control window size). CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: The local QUIC stack advertises two flow control limits to its remote peer: stream flow control limit and connection flow control limit. The remote peer must follow both limits w

    • Auf 4.0.3 aktualisieren
    Veröffentlicht Aktualisiert
  8. CVE-2026-72897

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

    Out-of-Bounds Access After SSL_set_SSL_CTX() During a Handshake

    Issue summary: A TLS server that calls SSL_set_SSL_CTX() to switch a connection to a different SSL_CTX part way through a handshake may access memory beyond the end of an internal array if the replacement context knows about more provider signature algorithms than the context the connection was created from. Applications which never call SSL_set_SSL_CTX() are not affected. Impact summary: A remote peer may be able to cause a small out-of-bounds read, and in some circumstances a fixed-value out-of-bounds write, on the server heap. This may lead to a Denial of Service. CWE: CWE-787: Out-of-bounds Write Description: A TLS connection records h

    • Auf 4.0.3 aktualisieren
    Veröffentlicht Aktualisiert
  9. CVE-2026-54875

    Niedrig · CVSS 3.7EPSS 0,29%Korrektur verfügbar

    Non-Constant-Time SM2 Scalar Multiplication on ARM64 and RISC-V

    Issue summary: A non-constant-time optimized implementation of scalar point multiplication is used for SM2 private key operations on ARM64 and RISC-V platforms. Impact summary: An attacker able to measure the time taken by, or to observe the cache-line access pattern of SM2 signing or decryption on an affected platform can learn information about the secret scalar. CWE: CWE-208: Observable Timing Discrepancy Description: On ARM64 and RISC-V processors, the SM2 curve uses an optimized scalar multiplication implementation whose conditional branches and table look ups are chosen according to the bits of the secret scalar. The execution time a

    • Auf 4.0.3 aktualisieren
    Veröffentlicht Aktualisiert
  10. CVE-2026-54873

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

    QUIC STREAM Fragment Metadata DoS

    Issue summary: QUIC process may keep memory for QUIC packet buffer for much longer period than necessary. Impact summary: Remote peer can exploit this vulnerability by sending maliciously crafted packets, making the local QUIC stack to keep the memory for packet buffers allocated. The time for which the memory remains allocated is entirely under the control of the potentially malicious remote peer. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: To save copy operation from the packet buffer to the stream reassemble buffer the QUIC stack leaves the stream data on the packet buffer waiting to be copied to a bu

    • Auf 4.0.3 aktualisieren
    Veröffentlicht Aktualisiert
  11. CVE-2026-54872

    Niedrig · CVSS 3.7EPSS 0,26%Korrektur verfügbar

    Timing Side-Channel in Scalar Multiplication for Non-NIST EC Curves

    Issue summary: The generic elliptic-curve scalar multiplication used for ECDSA and SM2 signature operations with curves that do not have a dedicated implementation leaks information about the secret nonce through timing. Impact summary: An attacker able to measure signing times may learn information about the per-signature secret nonce, which over many signatures can, via a lattice / Hidden Number Problem attack, lead to recovery of the private key. CWE: CWE-208: Observable Timing Discrepancy Description: The generic elliptic-curve scalar multiplication used for curves that do not have a dedicated constant-time implementation pads the secr

    • Auf 4.0.3 aktualisieren
    Veröffentlicht Aktualisiert
  12. CVE-2026-42772

    Mittel · CVSS 5.3EPSS 0,33%Korrektur verfügbar

    Potential CPU DoS via O(n^2) Fragment Reassembly in QUIC

    Issue summary: The QUIC stream reassembly algorithm performance deteriorates progressively as packets are arriving out of order. The worst case has a quadratic complexity proportional to the number of stream frames kept in the buffer for the received stream data. Impact summary: A remote QUIC peer that completes the handshake can create a connection-scoped CPU pressure and potentially a Denial of Service using compliant STREAM frames inside the advertised receive window, with low attacker bandwidth. CWE: CWE-407: Inefficient Algorithmic Complexity Description: OpenSSL manages received QUIC stream fragments using a doubly-linked list. While

    • Auf 4.0.3 aktualisieren
    Veröffentlicht Aktualisiert
  13. CVE-2026-35191

    Niedrig · CVSS 3.7EPSS 0,36%Korrektur verfügbar

    QUIC Unvalidated Amplification Credit may be Over Accounted

    Issue summary: The OpenSSL QUIC server, when configured to not preform address validation, can be forced to count incoming packets multiple times in its unvalidated credit computation, leading to a violation of the RFC 9000 unvalidated connection amplification limit of 3 times the amount of data received. Impact summary: A remote attacker able to spoof packets to a server using the OpenSSL QUIC implementation might use the server for an amplification of a DDoS attack. CWE: CWE-440: Expected Behavior Violation Description: OpenSSL's QUIC stack, when operating as a server, enforces client address validation (RFC 9000, Section 8), to confirm

    • Auf 4.0.3 aktualisieren
    Veröffentlicht Aktualisiert
  14. CVE-2026-35189

    Mittel · CVSS 5.3EPSS 0,27%Korrektur verfügbar

    Excessive Memory Allocation in Relative CRLDP Processing

    Issue summary: A certificate with many nameRelativeToCRLIssuer CRL distribution points causes disproportionate heap growth when OpenSSL caches X.509 extensions. Impact summary: Receiving a crafted certificate from a malicious peer can lead to significant memory pressure and possible Denial of Service in clients or in servers that solicit client certificates. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: A certificate or a set of certificates that fits under the limit for size of certificates accepted from the peer (~100 KiB) can result in allocation of several hundred MiB of resident memory on the receivin

    • Auf 4.0.3 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 →