Schwachstellen im Stack Netzwerkdienste · Seite 6

Stack buffer overflow in CMS (Auth)EnvelopedData parsing

Issue summary: Parsing CMS AuthEnvelopedData or EnvelopedData message with maliciously crafted AEAD parameters can trigger a stack buffer overflow. Impact summary: A stack buffer overflow may lead to a crash, causing Denial of Service, or potentially remote code execution. When parsing CMS (Auth)EnvelopedData structures that use AEAD ciphers such as AES-GCM, the IV (Initialization Vector) encoded in the ASN.1 parameters is copied into a fixed-size stack buffer without verifying that its length fits the destination. An attacker can supply a crafted CMS message with an oversized IV, causing a stack-based out-of-bounds write before any authent

• Auf 3.0.13-0ubuntu3.12+Fips1 aktualisieren
• Auf 3.0.13-0ubuntu3.7 aktualisieren
• Auf 3.0.18-1~deb12u2 aktualisieren
• Auf 3.0.19 aktualisieren
• Auf 3.0.2-0ubuntu1.21 aktualisieren
• Auf 3.0.2-0ubuntu1.21+Fips1 aktualisieren
• Auf 3.3.6 aktualisieren
• Auf 3.4.4 aktualisieren
• Auf 3.5.3-1ubuntu3 aktualisieren
• Auf 3.5.4-1~deb13u2 aktualisieren
• Auf 3.5.5 aktualisieren
• Auf 3.5.5-1 aktualisieren
• Auf 3.6.1 aktualisieren

Improper validation of PBMAC1 parameters in PKCS#12 MAC verification

Issue summary: PBMAC1 parameters in PKCS#12 files are missing validation which can trigger a stack-based buffer overflow, invalid pointer or NULL pointer dereference during MAC verification. Impact summary: The stack buffer overflow or NULL pointer dereference may cause a crash leading to Denial of Service for an application that parses untrusted PKCS#12 files. The buffer overflow may also potentially enable code execution depending on platform mitigations. When verifying a PKCS#12 file that uses PBMAC1 for the MAC, the PBKDF2 salt and keylength parameters from the file are used without validation. If the value of keylength exceeds the size

• Auf 3.4.4 aktualisieren
• Auf 3.5.3-1ubuntu3 aktualisieren
• Auf 3.5.4-1~deb13u2 aktualisieren
• Auf 3.5.5 aktualisieren
• Auf 3.5.5-1 aktualisieren
• Auf 3.5.5-1ubuntu1 aktualisieren
• Auf 3.6.1 aktualisieren

CoreDNS gRPC/HTTPS/HTTP3 servers lack resource limits, enabling DoS via unbounded connections and oversized messages

CoreDNS is a DNS server that chains plugins. Prior to version 1.14.0, multiple CoreDNS server implementations (gRPC, HTTPS, and HTTP/3) lack critical resource-limiting controls. An unauthenticated remote attacker can exhaust memory and degrade or crash the server by opening many concurrent connections, streams, or sending oversized request bodies. The issue is similar in nature to CVE-2025-47950 (QUIC DoS) but affects additional server types that do not enforce connection limits, stream limits, or message size constraints. Version 1.14.0 contains a patch.

CVE-2025-61985

ssh in OpenSSH before 10.1 allows the '\0' character in an ssh:// URI, potentially leading to code execution when a ProxyCommand is used.

• Auf 10.1 aktualisieren
• Auf 1:10.0p1-7+deb13u1 aktualisieren
• Auf 1:10.1p1-1 aktualisieren
• Auf 1:8.2p1-4ubuntu0.13+esm1 aktualisieren
• Auf 1:8.2p1-4ubuntu0.fips.0.13.1 aktualisieren
• Auf 1:8.9p1-3ubuntu0.14 aktualisieren
• Auf 1:9.2p1-2+deb12u8 aktualisieren

CVE-2025-61984

ssh in OpenSSH before 10.1 allows control characters in usernames that originate from certain possibly untrusted sources, potentially leading to code execution when a ProxyCommand is used. The untrusted sources are the command line and %-sequence expansion of a configuration file. (A configuration file that provides a complete literal username is not categorized as an untrusted source.)

• Auf 10.1 aktualisieren
• Auf 1:10.0p1-7+deb13u1 aktualisieren
• Auf 1:10.1p1-1 aktualisieren
• Auf 1:8.2p1-4ubuntu0.13+esm1 aktualisieren
• Auf 1:8.2p1-4ubuntu0.fips.0.13.1 aktualisieren
• Auf 1:9.2p1-2+deb12u8 aktualisieren

Out-of-bounds read in HTTP client no_proxy handling

Issue summary: An application using the OpenSSL HTTP client API functions may trigger an out-of-bounds read if the 'no_proxy' environment variable is set and the host portion of the authority component of the HTTP URL is an IPv6 address. Impact summary: An out-of-bounds read can trigger a crash which leads to Denial of Service for an application. The OpenSSL HTTP client API functions can be used directly by applications but they are also used by the OCSP client functions and CMP (Certificate Management Protocol) client implementation in OpenSSL. However the URLs used by these implementations are unlikely to be controlled by an attacker. In

• Auf 2025.02-8ubuntu3 aktualisieren
• Auf 3.0.17-1~deb12u3 aktualisieren
• Auf 3.0.18 aktualisieren
• Auf 3.2.6 aktualisieren
• Auf 3.3.5 aktualisieren
• Auf 3.4.3 aktualisieren
• Auf 3.5.1-1+deb13u1 aktualisieren
• Auf 3.5.3-1ubuntu2 aktualisieren
• Auf 3.5.4 aktualisieren
• Auf 3.5.4-1 aktualisieren

Timing side-channel in SM2 algorithm on 64 bit ARM

Issue summary: A timing side-channel which could potentially allow remote recovery of the private key exists in the SM2 algorithm implementation on 64 bit ARM platforms. Impact summary: A timing side-channel in SM2 signature computations on 64 bit ARM platforms could allow recovering the private key by an attacker.. While remote key recovery over a network was not attempted by the reporter, timing measurements revealed a timing signal which may allow such an attack. OpenSSL does not directly support certificates with SM2 keys in TLS, and so this CVE is not relevant in most TLS contexts. However, given that it is possible to add support fo

• Auf 3.2.6 aktualisieren
• Auf 3.3.5 aktualisieren
• Auf 3.4.3 aktualisieren
• Auf 3.5.1-1+deb13u1 aktualisieren
• Auf 3.5.3-1ubuntu2 aktualisieren
• Auf 3.5.4 aktualisieren
• Auf 3.5.4-1 aktualisieren

Out-of-bounds read & write in RFC 3211 KEK Unwrap

Issue summary: An application trying to decrypt CMS messages encrypted using password based encryption can trigger an out-of-bounds read and write. Impact summary: This out-of-bounds read may trigger a crash which leads to Denial of Service for an application. The out-of-bounds write can cause a memory corruption which can have various consequences including a Denial of Service or Execution of attacker-supplied code. Although the consequences of a successful exploit of this vulnerability could be severe, the probability that the attacker would be able to perform it is low. Besides, password based (PWRI) encryption support in CMS messages is

• Auf 1.0.1f-1ubuntu2.27+esm11 aktualisieren
• Auf 1.0.2g-1ubuntu4.20+esm13 aktualisieren
• Auf 1.0.2g-1ubuntu4.fips.4.20.13 aktualisieren
• Auf 1.0.2n-1ubuntu5.13+esm2 aktualisieren
• Auf 1.0.2zm aktualisieren
• Auf 1.1.1-1ubuntu2.1~18.04.23+esm6 aktualisieren
• Auf 1.1.1-1ubuntu2.fips.2.1~18.04.23.6 aktualisieren
• Auf 1.1.1f-1ubuntu2.24+esm1 aktualisieren
• Auf 1.1.1f-1ubuntu2.fips.24.1 aktualisieren
• Auf 1.1.1zd aktualisieren
• Auf 3.0.17-1~deb12u3 aktualisieren
• Auf 3.0.18 aktualisieren
• Auf 3.2.6 aktualisieren
• Auf 3.3.5 aktualisieren
• Auf 3.4.3 aktualisieren
• Auf 3.5.1-1+deb13u1 aktualisieren
• Auf 3.5.4 aktualisieren
• Auf 3.5.4-1 aktualisieren

CoreDNS: DNS Cache Pinning via etcd Lease ID Confusion

CoreDNS is a DNS server that chains plugins. Starting in version 1.2.0 and prior to version 1.12.4, the CoreDNS etcd plugin contains a TTL confusion vulnerability where lease IDs are incorrectly used as TTL values, enabling DNS cache pinning attacks. This effectively creates a DoS condition for DNS resolution of affected services. The `TTL()` function in `plugin/etcd/etcd.go` incorrectly casts etcd lease IDs (64-bit integers) to uint32 and uses them as TTL values. Large lease IDs become very large TTLs when cast to uint32. This enables cache pinning attacks. Version 1.12.4 contains a fix for the issue.

CoreDNS Vulnerable to DoQ Memory Exhaustion via Stream Amplification

CoreDNS is a DNS server that chains plugins. In versions prior to 1.12.2, a Denial of Service (DoS) vulnerability exists in the CoreDNS DNS-over-QUIC (DoQ) server implementation. The server previously created a new goroutine for every incoming QUIC stream without imposing any limits on the number of concurrent streams or goroutines. A remote, unauthenticated attacker could open a large number of streams, leading to uncontrolled memory consumption and eventually causing an Out Of Memory (OOM) crash — especially in containerized or memory-constrained environments. The patch in version 1.12.2 introduces two key mitigation mechanisms: `max_stream

The x509 application adds trusted use instead of rejected use

Issue summary: Use of -addreject option with the openssl x509 application adds a trusted use instead of a rejected use for a certificate. Impact summary: If a user intends to make a trusted certificate rejected for a particular use it will be instead marked as trusted for that use. A copy & paste error during minor refactoring of the code introduced this issue in the OpenSSL 3.5 version. If, for example, a trusted CA certificate should be trusted only for the purpose of authenticating TLS servers but not for CMS signature verification and the CMS signature verification is intended to be marked as rejected with the -addreject option, the res

• Auf 3.5.0-2 aktualisieren
• Auf 3.5.1 aktualisieren

CVE-2025-32728

In sshd in OpenSSH before 10.0, the DisableForwarding directive does not adhere to the documentation stating that it disables X11 and agent forwarding.

• Auf 10.0 aktualisieren
• Auf 1:10.0p1-1 aktualisieren
• Auf 1:8.2p1-4ubuntu0.13 aktualisieren
• Auf 1:8.2p1-4ubuntu0.fips.0.13 aktualisieren
• Auf 1:8.9p1-3ubuntu0.13 aktualisieren
• Auf 1:8.9p1-3ubuntu0.13+Fips1 aktualisieren
• Auf 1:9.2p1-2+deb12u6 aktualisieren

RFC7250 handshakes with unauthenticated servers don't abort as expected

Issue summary: Clients using RFC7250 Raw Public Keys (RPKs) to authenticate a server may fail to notice that the server was not authenticated, because handshakes don't abort as expected when the SSL_VERIFY_PEER verification mode is set. Impact summary: TLS and DTLS connections using raw public keys may be vulnerable to man-in-middle attacks when server authentication failure is not detected by clients. RPKs are disabled by default in both TLS clients and TLS servers. The issue only arises when TLS clients explicitly enable RPK use by the server, and the server, likewise, enables sending of an RPK instead of an X.509 certificate chain. The

• Auf 3.2.4 aktualisieren
• Auf 3.3.3 aktualisieren
• Auf 3.4.1 aktualisieren
• Auf 3.4.1-1 aktualisieren
• Auf 44.0.1 aktualisieren

Timing side-channel in ECDSA signature computation

Issue summary: A timing side-channel which could potentially allow recovering the private key exists in the ECDSA signature computation. Impact summary: A timing side-channel in ECDSA signature computations could allow recovering the private key by an attacker. However, measuring the timing would require either local access to the signing application or a very fast network connection with low latency. There is a timing signal of around 300 nanoseconds when the top word of the inverted ECDSA nonce value is zero. This can happen with significant probability only for some of the supported elliptic curves. In particular the NIST P-521 curve is

• Auf 1.0.2zl aktualisieren
• Auf 1.1.1f-1ubuntu2.24 aktualisieren
• Auf 1.1.1zb aktualisieren
• Auf 2025.02-8+deb13u1 aktualisieren
• Auf 2025.02-9 aktualisieren
• Auf 3.0.16 aktualisieren
• Auf 3.0.16-1~deb12u1 aktualisieren
• Auf 3.1.8 aktualisieren
• Auf 3.2.4 aktualisieren
• Auf 3.3.3 aktualisieren
• Auf 3.4.1 aktualisieren
• Auf 3.4.1-1 aktualisieren

Use After Free with SSL_free_buffers

Issue summary: Calling the OpenSSL API function SSL_free_buffers may cause memory to be accessed that was previously freed in some situations Impact summary: A use after free can have a range of potential consequences such as the corruption of valid data, crashes or execution of arbitrary code. However, only applications that directly call the SSL_free_buffers function are affected by this issue. Applications that do not call this function are not vulnerable. Our investigations indicate that this function is rarely used by applications. The SSL_free_buffers function is used to free the internal OpenSSL buffer used when processing an incomin

• Auf 1.1.1f-1ubuntu2.23 aktualisieren
• Auf 1.1.1y aktualisieren
• Auf 3.0.14 aktualisieren
• Auf 3.0.14-1~deb12u1 aktualisieren
• Auf 3.1.6 aktualisieren
• Auf 3.2.2 aktualisieren
• Auf 3.2.2-1 aktualisieren
• Auf 3.3.1 aktualisieren

Low-level invalid GF(2^m) parameters lead to OOB memory access

Issue summary: Use of the low-level GF(2^m) elliptic curve APIs with untrusted explicit values for the field polynomial can lead to out-of-bounds memory reads or writes. Impact summary: Out of bound memory writes can lead to an application crash or even a possibility of a remote code execution, however, in all the protocols involving Elliptic Curve Cryptography that we're aware of, either only "named curves" are supported, or, if explicit curve parameters are supported, they specify an X9.62 encoding of binary (GF(2^m)) curves that can't represent problematic input values. Thus the likelihood of existence of a vulnerable application is low.

• Auf 1.0.2zl aktualisieren
• Auf 1.1.1zb aktualisieren
• Auf 3.0.15-1~deb12u1 aktualisieren
• Auf 3.0.16 aktualisieren
• Auf 3.1.8 aktualisieren
• Auf 3.2.4 aktualisieren
• Auf 3.3.2-2 aktualisieren
• Auf 3.3.3 aktualisieren

Possible denial of service in X.509 name checks

Issue summary: Applications performing certificate name checks (e.g., TLS clients checking server certificates) may attempt to read an invalid memory address resulting in abnormal termination of the application process. Impact summary: Abnormal termination of an application can a cause a denial of service. Applications performing certificate name checks (e.g., TLS clients checking server certificates) may attempt to read an invalid memory address when comparing the expected name with an `otherName` subject alternative name of an X.509 certificate. This may result in an exception that terminates the application program. Note that basic cert

• Auf 2024.02-2ubuntu0.6 aktualisieren
• Auf 3.0.13-0ubuntu3.4 aktualisieren
• Auf 3.0.13-0ubuntu3.6+Fips1 aktualisieren
• Auf 3.0.14-1~deb12u2 aktualisieren
• Auf 3.0.15 aktualisieren
• Auf 3.0.2-0ubuntu1.18 aktualisieren
• Auf 3.0.2-0ubuntu1.18+Fips1 aktualisieren
• Auf 3.1.7 aktualisieren
• Auf 3.2.3 aktualisieren
• Auf 3.3.2 aktualisieren
• Auf 3.3.2-1 aktualisieren

SSL_select_next_proto buffer overread

Issue summary: Calling the OpenSSL API function SSL_select_next_proto with an empty supported client protocols buffer may cause a crash or memory contents to be sent to the peer. Impact summary: A buffer overread can have a range of potential consequences such as unexpected application beahviour or a crash. In particular this issue could result in up to 255 bytes of arbitrary private data from memory being sent to the peer leading to a loss of confidentiality. However, only applications that directly call the SSL_select_next_proto function with a 0 length list of supported client protocols are affected by this issue. This would normally neve

• Auf 1.0.1f-1ubuntu2.27+esm16 aktualisieren
• Auf 1.0.2g-1ubuntu4.20+esm18 aktualisieren
• Auf 1.0.2n-1ubuntu5.13+esm6 aktualisieren
• Auf 1.0.2zk aktualisieren
• Auf 1.1.1-1ubuntu2.1~18.04.23+esm10 aktualisieren
• Auf 1.1.1za aktualisieren
• Auf 3.0.15 aktualisieren
• Auf 3.0.15-1~deb12u1 aktualisieren
• Auf 3.1.7 aktualisieren
• Auf 3.2.3 aktualisieren
• Auf 3.3.2 aktualisieren
• Auf 3.3.2-1 aktualisieren

Excessive time spent checking DSA keys and parameters

Issue summary: Checking excessively long DSA keys or parameters may be very slow. Impact summary: Applications that use the functions EVP_PKEY_param_check() or EVP_PKEY_public_check() to check a DSA public key or DSA parameters may experience long delays. Where the key or parameters that are being checked have been obtained from an untrusted source this may lead to a Denial of Service. The functions EVP_PKEY_param_check() or EVP_PKEY_public_check() perform various checks on DSA parameters. Some of those computations take a long time if the modulus (`p` parameter) is too large. Trying to use a very large modulus is slow and OpenSSL will not

• Auf 3.0.13-0ubuntu3.2 aktualisieren
• Auf 3.0.13-0ubuntu3.6+Fips1 aktualisieren
• Auf 3.0.14 aktualisieren
• Auf 3.0.14-1~deb12u1 aktualisieren
• Auf 3.0.2-0ubuntu1.17 aktualisieren
• Auf 3.0.2-0ubuntu1.17+Fips1 aktualisieren
• Auf 3.1.6 aktualisieren
• Auf 3.2.2 aktualisieren
• Auf 3.2.2-1 aktualisieren
• Auf 3.3.1 aktualisieren

Excessive time spent checking invalid RSA public keys

Issue summary: Checking excessively long invalid RSA public keys may take a long time. Impact summary: Applications that use the function EVP_PKEY_public_check() to check RSA public keys may experience long delays. Where the key that is being checked has been obtained from an untrusted source this may lead to a Denial of Service. When function EVP_PKEY_public_check() is called on RSA public keys, a computation is done to confirm that the RSA modulus, n, is composite. For valid RSA keys, n is a product of two or more large primes and this computation completes quickly. However, if n is an overly large prime, then this computation would take

• Auf 2024.02-2ubuntu0.6 aktualisieren
• Auf 3.0.10-1ubuntu4 aktualisieren
• Auf 3.0.13 aktualisieren
• Auf 3.0.13-1~deb12u1 aktualisieren
• Auf 3.0.2-0ubuntu1.14 aktualisieren
• Auf 3.0.2-0ubuntu1.14+Fips1 aktualisieren
• Auf 3.1.5 aktualisieren
• Auf 3.1.5-1 aktualisieren
• Auf 3.2.1 aktualisieren