Сетевые службы: уязвимости стека · Страница 4

Possible NULL Dereference in Password-Based CMS Decryption

Issue summary: A specially crafted password-encrypted CMS message can trigger a NULL pointer dereference during CMS decryption. Impact summary: This NULL pointer dereference leads to an application crash and a Denial of Service. The CMS PasswordRecipientInfo.keyDerivationAlgorithm field is defined as OPTIONAL in the ASN.1 specification and may therefore be absent in specially crafted inputs. During the password-based CMS decryption the OpenSSL CMS implementation dereferences this field without first checking whether it was present. An attacker who supplies such a CMS message to an application performing password-based CMS decryption can tr

• Обновитесь до 1.0.1f-1ubuntu2.27+esm14
• Обновитесь до 1.0.2g-1ubuntu4.20+esm16
• Обновитесь до 1.0.2n-1ubuntu5.13+esm5
• Обновитесь до 1.0.2zq
• Обновитесь до 1.1.1-1ubuntu2.1~18.04.23+esm9
• Обновитесь до 1.1.1-1ubuntu2.fips.2.1~18.04.23.9
• Обновитесь до 1.1.1zh
• Обновитесь до 3.0.20-1~deb12u2
• Обновитесь до 3.0.21
• Обновитесь до 3.4.6
• Обновитесь до 3.5.6-1~deb13u2
• Обновитесь до 3.5.7
• Обновитесь до 3.6.3
• Обновитесь до 3.6.3-1
• Обновитесь до 4.0.1

NULL Dereference in Certificate Verification with OCSP Checking

Issue summary: When a partial-chain certificate verification is enabled together with OCSP response checking for the whole chain, a NULL dereference will happen if the verified chain does not have a self-signed trusted anchor, crashing the process. Impact summary: A NULL pointer dereference can trigger a crash which leads to a Denial of Service for an application. When performing OCSP response checking for certificates in the verification chain, the code always tries to access the next certificate as the issuer. There is a check for a self-signed certificate. However with the partial chain verification enabled when the chain does not have a

• Обновитесь до 3.6.3
• Обновитесь до 3.6.3-1
• Обновитесь до 4.0.1

NULL Pointer Dereference in QUIC Server Initial Packet Handling

Issue summary: Receiving a QUIC initial packet with an invalid token may trigger a NULL pointer dereference in the OpenSSL QUIC server with address validation disabled. Impact summary: NULL pointer dereference typically causes abnormal termination of the affected QUIC server process and a Denial of Service. If the address validation is disabled in the OpenSSL QUIC server implementation, an attacker can crash the server by sending an initial packet with an invalid or expired token. By default, the client address validation is enabled in the OpenSSL QUIC server implementation, which makes the default configuration not vulnerable to this issu

• Обновитесь до 3.5.3-1ubuntu3.4
• Обновитесь до 3.5.5-1ubuntu3.2
• Обновитесь до 3.5.6-1~deb13u2
• Обновитесь до 3.5.7
• Обновитесь до 3.6.3
• Обновитесь до 3.6.3-1
• Обновитесь до 4.0.1

Double-free When Checking OCSP Stapled Response

Issue summary: A malicious server can exploit TLS OCSP stapling by delivering a crafted response through the status_request extension, triggering a double-free in the client's certificate verification path. Impact summary: Successful exploitation allows an attacker to corrupt heap memory via a double-free, potentially leading to a Denial of Service or possibly an attacker controlled code execution or other undefined behavior. If OCSP stapling is enabled and the TLS client connects to a malicious server, a crafted OCSP stapled response can trigger a double free in the TLS client when the stapled response is checked. The OCSP stapling is not

• Обновитесь до 3.6.3
• Обновитесь до 3.6.3-1
• Обновитесь до 4.0.1

Unbounded Memory Growth in the QUIC PATH_CHALLENGE Handler

Issue summary: Remote peer may exhaust heap memory of the QUIC server or client by flooding it with packets containing PATH_CHALLENGE frames. Impact summary: A malicious remote peer can cause an unbounded memory allocation which can lead to an abnormal termination of the application acting as a QUIC client or server and a Denial of Service. A remote peer may exhaust heap memory by flooding the local QUIC stack with PATH_CHALLENGE frames. The local QUIC stack allocates a PATH_RESPONSE frame for every PATH_CHALLENGE it receives. The allocated PATH_RESPONSE frame gets freed only when the remote peer acknowledges reception of the PATH_RESPONSE

• Обновитесь до 3.4.6
• Обновитесь до 3.5.3-1ubuntu3.4
• Обновитесь до 3.5.5-1ubuntu3.2
• Обновитесь до 3.5.6-1~deb13u2
• Обновитесь до 3.5.7
• Обновитесь до 3.6.3
• Обновитесь до 3.6.3-1
• Обновитесь до 4.0.1

CMS AuthEnvelopedData Processing May Accept Forged Messages

Issue Summary: Cryptographic Message Services (CMS) processing fails to perform sufficient input validation on the cipher and tag length fields of AuthEnvelopedData containers, leading to various potential compromises. Impact Summary: Attackers making use of these vulnerabilities may achieve key-equivalent functionality for a given CMS recipient and/or bypass integrity validation for a given message. In one use case, an attacker may send a CMS message containing AuthEnvelopedData with the cipher specified as a non-AEAD cipher. OpenSSL erroneously allows this selection, and attempts to decrypt and validate the message. An on-path attacker

• Обновитесь до 3.0.13-0ubuntu3.11
• Обновитесь до 3.0.13-0ubuntu3.12+Fips1
• Обновитесь до 3.0.2-0ubuntu1.25
• Обновитесь до 3.0.2-0ubuntu1.25+Fips1
• Обновитесь до 3.0.20-1~deb12u2
• Обновитесь до 3.0.21
• Обновитесь до 3.4.6
• Обновитесь до 3.5.3-1ubuntu3.4
• Обновитесь до 3.5.6-1~deb13u2
• Обновитесь до 3.5.7
• Обновитесь до 3.6.3
• Обновитесь до 3.6.3-1
• Обновитесь до 4.0.1

PKCS#12 Files with PBMAC1 Are Accepted with Short HMAC Keys

Issue Summary: The PKCS#12 file processing fails to perform sufficient input validation for files that use Password-Based Message Authentication Code 1 (PBMAC1) integrity mechanism allowing a certificate and private key forgery. Impact Summary: An attacker impersonating a user can cause a service reading PKCS#12 files to accept forged certificates and private keys with a 1 in 256 probability. If a service accepting PKCS#12 files is using passwords for authenticating the received files, the attacker can create unencrypted PKCS#12 files that use PBMAC1 authentication that specifies an HMAC key of only one byte, allowing them to craft a file t

• Обновитесь до 3.4.6
• Обновитесь до 3.5.3-1ubuntu3.4
• Обновитесь до 3.5.5-1ubuntu3.2
• Обновитесь до 3.5.6-1~deb13u2
• Обновитесь до 3.5.7
• Обновитесь до 3.6.3
• Обновитесь до 3.6.3-1
• Обновитесь до 4.0.1

Heap Buffer Over-read in ASN.1 Content Parsing

Issue summary: Parsing a crafted DER-encoded ASN.1 structure with a primitive element whose content exceeds 2 gigabytes in length may cause a heap buffer over-read on 64-bit Unix and Unix-like platforms. Impact summary: The heap buffer over-read may crash the application (Denial of Service) or to load into the decoded ASN.1 object contents of memory beyond the end of the input buffer. More typically such ASN.1 elements would instead be truncated. An integer truncation in OpenSSL's ASN.1 decoder causes the content length of an ASN.1 primitive element to be mishandled when it exceeds 2 gigabytes. In the worst case the truncated length is tre

• Обновитесь до 1.0.1f-1ubuntu2.27+esm14
• Обновитесь до 1.0.2g-1ubuntu4.20+esm16
• Обновитесь до 1.0.2n-1ubuntu5.13+esm5
• Обновитесь до 1.0.2zq
• Обновитесь до 1.1.1-1ubuntu2.1~18.04.23+esm9
• Обновитесь до 1.1.1-1ubuntu2.fips.2.1~18.04.23.9
• Обновитесь до 1.1.1zh
• Обновитесь до 3.0.20-1~deb12u2
• Обновитесь до 3.0.21
• Обновитесь до 3.4.6
• Обновитесь до 3.5.6-1~deb13u2
• Обновитесь до 3.5.7
• Обновитесь до 3.6.3
• Обновитесь до 3.6.3-1
• Обновитесь до 4.0.1

Out-of-Bounds Read in CMS Password-Based Decryption

Issue summary: When CMS password-based decryption (RFC 3211 / PWRI key unwrap) processes attacker-supplied CMS data, an attacker-chosen stream-mode KEK cipher can trigger a heap out-of-bounds read in kek_unwrap_key(). Impact summary: A heap buffer over-read may trigger a crash which leads to Denial of Service for an application if the input buffer ends at a memory page boundary and the following page is unmapped. There is no information disclosure as the over-read bytes are not revealed to the attacker. The key unwrapping function performs a check-byte test as specified in the RFC that reads 7 bytes from a heap allocation that is based on t

• Обновитесь до 1.0.1f-1ubuntu2.27+esm14
• Обновитесь до 1.0.2g-1ubuntu4.20+esm16
• Обновитесь до 1.0.2n-1ubuntu5.13+esm5
• Обновитесь до 1.0.2zq
• Обновитесь до 1.1.1-1ubuntu2.1~18.04.23+esm9
• Обновитесь до 1.1.1-1ubuntu2.fips.2.1~18.04.23.9
• Обновитесь до 1.1.1zh
• Обновитесь до 3.0.20-1~deb12u2
• Обновитесь до 3.0.21
• Обновитесь до 3.4.6
• Обновитесь до 3.5.6-1~deb13u2
• Обновитесь до 3.5.7
• Обновитесь до 3.6.3
• Обновитесь до 3.6.3-1
• Обновитесь до 4.0.1

Possible Heap Buffer Overflow in ASN.1 Multibyte String Conversion

Issue summary: A signed integer overflow when sizing the destination buffer for Unicode output in ASN1_mbstring_ncopy() can lead to a heap buffer overflow. Impact summary: A heap buffer overflow may lead to a crash or possibly attacker controlled code execution or other undefined behaviour. In ASN1_mbstring_copy() and ASN1_mbstring_ncopy() the destination size for Unicode output is computed in a signed int: by left shift of the input character count for BMPSTRING (UTF-16) and UNIVERSALSTRING (UTF-32), and by summing per-character byte counts for UTF8STRING. The calculation overflows when the input reaches around 2^30 characters. In the wors

• Обновитесь до 1.0.1f-1ubuntu2.27+esm14
• Обновитесь до 1.0.2g-1ubuntu4.20+esm16
• Обновитесь до 1.0.2n-1ubuntu5.13+esm5
• Обновитесь до 1.0.2zq
• Обновитесь до 1.1.1-1ubuntu2.1~18.04.23+esm9
• Обновитесь до 1.1.1-1ubuntu2.fips.2.1~18.04.23.9
• Обновитесь до 1.1.1zh
• Обновитесь до 3.0.20-1~deb12u2
• Обновитесь до 3.0.21
• Обновитесь до 3.4.6
• Обновитесь до 3.5.6-1~deb13u2
• Обновитесь до 3.5.7
• Обновитесь до 3.6.3
• Обновитесь до 3.6.3-1
• Обновитесь до 4.0.1

CoreDNS TSIG authentication bypass on gRPC, QUIC, DoH, and DoH3 transports

CoreDNS is a DNS server written in Go. In versions prior to 1.14.3, the gRPC, QUIC, DoH, and DoH3 transport implementations incorrectly handle TSIG authentication. For gRPC and QUIC, the server checks whether the TSIG key name exists in the configuration but never calls dns.TsigVerify() to validate the HMAC. If the key name matches a configured key, the tsigStatus field remains nil and the tsig plugin treats the request as successfully authenticated regardless of the MAC value. For DoH and DoH3, the issue is more severe: the DoHWriter.TsigStatus() method unconditionally returns nil, and the server never inspects the TSIG record at all. Any re

CoreDNS transfer plugin subzone ACL bypass via lexicographic zone comparison

CoreDNS is a DNS server that chains plugins. In versions prior to 1.14.3, the transfer plugin can select the wrong ACL stanza when both a parent zone and a more-specific subzone are configured. The longestMatch() function in plugin/transfer/transfer.go uses a lexicographic string comparison instead of an actual longest-suffix match to select the winning zone. As a result, a permissive parent-zone transfer rule can override a restrictive subzone rule depending on zone name ordering (e.g., "example.org." > "a.example.org." lexicographically). This allows an unauthorized remote client to perform AXFR/IXFR for the subzone and retrieve its full zo

CoreDNS DoH GET path missing size validation causes CPU and memory amplification

CoreDNS is a DNS server that chains plugins. In versions prior to 1.14.3, the DNS-over-HTTPS (DoH) GET path accepts oversized dns= query parameter values and performs URL query parsing, base64 decoding, and DNS message unpacking before rejecting the request. Unlike the POST path, which applies a bounded read via http.MaxBytesReader limited to 65536 bytes, the GET path has no equivalent size validation before expensive processing. A remote, unauthenticated attacker can repeatedly send oversized DoH GET requests to force high CPU usage, large transient memory allocations, and elevated garbage-collection pressure, leading to denial of service. T

CoreDNS DNS-over-QUIC unbounded goroutine growth leads to denial of service

CoreDNS is a DNS server that chains plugins. In versions prior to 1.14.3, the DNS-over-QUIC (DoQ) server can be driven into unbounded goroutine and memory growth by a remote client that opens many QUIC streams and sends only 1 byte per stream. When the worker pool is full, CoreDNS still spawns a goroutine per accepted stream to wait for a worker token. Additionally, active workers block indefinitely in io.ReadFull() with no per-stream read deadline, allowing an attacker to pin all workers by sending a single byte so the read blocks waiting for the second byte of the DoQ length prefix. This enables an unauthenticated remote attacker to cause m

CoreDNS TSIG authentication bypass on encrypted DNS transports

CoreDNS is a DNS server that chains plugins. In versions prior to 1.14.3, the tsig plugin can be bypassed on non-plain-DNS transports (DoT, DoH, DoH3, DoQ, and gRPC) because it trusts the transport writer's TsigStatus() instead of performing verification itself. The DoH and DoH3 writer's TsigStatus() always returns nil, the DoT server does not set TsigSecret on the dns.Server, and the DoQ and gRPC writers also unconditionally return nil. This allows an unauthenticated remote client to bypass TSIG-based authentication and access resources intended to be restricted behind a tsig require all policy. Plain DNS over TCP and UDP are not affected. T

Incorrect Failure Handling in RSA KEM RSASVE Encapsulation

Issue summary: Applications using RSASVE key encapsulation to establish a secret encryption key can send contents of an uninitialized memory buffer to a malicious peer. Impact summary: The uninitialized buffer might contain sensitive data from the previous execution of the application process which leads to sensitive data leakage to an attacker. RSA_public_encrypt() returns the number of bytes written on success and -1 on error. The affected code tests only whether the return value is non-zero. As a result, if RSA encryption fails, encapsulation can still return success to the caller, set the output lengths, and leave the caller to use the

• Обновитесь до 3.0.13-0ubuntu3.12+Fips1
• Обновитесь до 3.0.13-0ubuntu3.9
• Обновитесь до 3.0.19-1~deb12u2
• Обновитесь до 3.0.2-0ubuntu1.23
• Обновитесь до 3.0.20
• Обновитесь до 3.3.7
• Обновитесь до 3.4.5
• Обновитесь до 3.5.3-1ubuntu3.3
• Обновитесь до 3.5.5-1~deb13u2
• Обновитесь до 3.5.6
• Обновитесь до 3.6.2
• Обновитесь до 3.6.2-1

Heap Buffer Overflow in Hexadecimal Conversion

Issue summary: Converting an excessively large OCTET STRING value to a hexadecimal string leads to a heap buffer overflow on 32 bit platforms. Impact summary: A heap buffer overflow may lead to a crash or possibly an attacker controlled code execution or other undefined behavior. If an attacker can supply a crafted X.509 certificate with an excessively large OCTET STRING value in extensions such as the Subject Key Identifier (SKID) or Authority Key Identifier (AKID) which are being converted to hex, the size of the buffer needed for the result is calculated as multiplication of the input length by 3. On 32 bit platforms, this multiplication

• Обновитесь до 3.0.13-0ubuntu3.12+Fips1
• Обновитесь до 3.0.13-0ubuntu3.9
• Обновитесь до 3.0.19-1~deb12u2
• Обновитесь до 3.0.2-0ubuntu1.23
• Обновитесь до 3.0.20
• Обновитесь до 3.3.7
• Обновитесь до 3.4.5
• Обновитесь до 3.5.3-1ubuntu3.3
• Обновитесь до 3.5.5-1~deb13u2
• Обновитесь до 3.5.6
• Обновитесь до 3.6.2
• Обновитесь до 3.6.2-1

Possible NULL Dereference When Processing CMS KeyTransportRecipientInfo

Issue summary: During processing of a crafted CMS EnvelopedData message with KeyTransportRecipientInfo a NULL pointer dereference can happen. Impact summary: Applications that process attacker-controlled CMS data may crash before authentication or cryptographic operations occur resulting in Denial of Service. When a CMS EnvelopedData message that uses KeyTransportRecipientInfo with RSA-OAEP encryption is processed, the optional parameters field of RSA-OAEP SourceFunc algorithm identifier is examined without checking for its presence. This results in a NULL pointer dereference if the field is missing. Applications and services that call CMS

• Обновитесь до 1.0.2g-1ubuntu4.20+esm15
• Обновитесь до 1.0.2g-1ubuntu4.fips.4.20.15
• Обновитесь до 1.0.2n-1ubuntu5.13+esm4
• Обновитесь до 1.0.2zp
• Обновитесь до 1.1.1-1ubuntu2.1~18.04.23+esm8
• Обновитесь до 1.1.1-1ubuntu2.fips.2.1~18.04.23.8
• Обновитесь до 1.1.1zg
• Обновитесь до 3.0.19-1~deb12u2
• Обновитесь до 3.0.20
• Обновитесь до 3.3.7
• Обновитесь до 3.4.5
• Обновитесь до 3.5.5-1~deb13u2
• Обновитесь до 3.5.6
• Обновитесь до 3.6.2
• Обновитесь до 3.6.2-1

Possible NULL Dereference When Processing CMS KeyAgreeRecipientInfo

Issue summary: During processing of a crafted CMS EnvelopedData message with KeyAgreeRecipientInfo a NULL pointer dereference can happen. Impact summary: Applications that process attacker-controlled CMS data may crash before authentication or cryptographic operations occur resulting in Denial of Service. When a CMS EnvelopedData message that uses KeyAgreeRecipientInfo is processed, the optional parameters field of KeyEncryptionAlgorithmIdentifier is examined without checking for its presence. This results in a NULL pointer dereference if the field is missing. Applications and services that call CMS_decrypt() on untrusted input (e.g., S/MI

• Обновитесь до 1.0.2g-1ubuntu4.20+esm15
• Обновитесь до 1.0.2g-1ubuntu4.fips.4.20.15
• Обновитесь до 1.0.2n-1ubuntu5.13+esm4
• Обновитесь до 1.0.2zp
• Обновитесь до 1.1.1-1ubuntu2.1~18.04.23+esm8
• Обновитесь до 1.1.1-1ubuntu2.fips.2.1~18.04.23.8
• Обновитесь до 1.1.1zg
• Обновитесь до 3.0.19-1~deb12u2
• Обновитесь до 3.0.20
• Обновитесь до 3.3.7
• Обновитесь до 3.4.5
• Обновитесь до 3.5.5-1~deb13u2
• Обновитесь до 3.5.6
• Обновитесь до 3.6.2
• Обновитесь до 3.6.2-1

NULL Pointer Dereference When Processing a Delta CRL

Issue summary: When a delta CRL that contains a Delta CRL Indicator extension is processed a NULL pointer dereference might happen if the required CRL Number extension is missing. Impact summary: A NULL pointer dereference can trigger a crash which leads to a Denial of Service for an application. When CRL processing and delta CRL processing is enabled during X.509 certificate verification, the delta CRL processing does not check whether the CRL Number extension is NULL before dereferencing it. When a malformed delta CRL file is being processed, this parameter can be NULL, causing a NULL pointer dereference. Exploiting this issue requires t

• Обновитесь до 1.0.1f-1ubuntu2.27+esm13
• Обновитесь до 1.0.2g-1ubuntu4.20+esm15
• Обновитесь до 1.0.2g-1ubuntu4.fips.4.20.15
• Обновитесь до 1.0.2n-1ubuntu5.13+esm4
• Обновитесь до 1.0.2zp
• Обновитесь до 1.1.1-1ubuntu2.1~18.04.23+esm8
• Обновитесь до 1.1.1-1ubuntu2.fips.2.1~18.04.23.8
• Обновитесь до 1.1.1zg
• Обновитесь до 3.0.19-1~deb12u2
• Обновитесь до 3.0.20
• Обновитесь до 3.3.7
• Обновитесь до 3.4.5
• Обновитесь до 3.5.5-1~deb13u2
• Обновитесь до 3.5.6
• Обновитесь до 3.6.2
• Обновитесь до 3.6.2-1