EulerOS 2.0 SP15 : openssl (EulerOS-SA-2026-5194)

critical Nessus Plugin ID 383292

Synopsis

The remote EulerOS host is missing multiple security updates.

Description

According to the versions of the openssl packages installed, the EulerOS installation on the remote host is affected by the following vulnerabilities :

Issue summary: ChaCha20-Poly1305 and AES-OCB decryption with an empty_x000D_ ciphertext can report success without verifying the supplied authentication_x000D_ tag when the operation is finalized by calling the EVP_Cipher() function._x000D_
_x000D_ Impact summary: Applications calling EVP_Cipher() on an empty ciphertext and_x000D_ expecting the call to check the AEAD tag may accept forged messages._x000D_
_x000D_ CWE: CWE-354 (Improper Validation of Integrity Check Value)_x000D_
_x000D_ Description: The EVP_Cipher() API call for AEAD ciphers behaves like a one_x000D_ shot encryption and decryption call. It also verifies the AEAD tag after the_x000D_ decryption operation. However for AES-OCB and ChaCha20-Poly1305 ciphers_x000D_ it skipped the AEAD tag verification when an empty ciphertext was passed to_x000D_ the function. The callers of this function might believe that a successful_x000D_ return indicates a valid AEAD tag for these ciphers, even when that has not_x000D_ truly been validated in this case._x000D_
_x000D_ FIPS impact: no_x000D_ The FIPS modules in 4.0, 3.6, 3.5, 3.4, and 3.0 are not affected by this CVE_x000D_ as the affected algorithms are not FIPS approved and thus not implemented_x000D_ in the FIPS module.(CVE-2026-75803)

Issue summary: OpenSSL CMP password based protection verification only_x000D_ checks whether the protectionAlg parameter was not NULL and not its_x000D_ ASN.1 type, before treating it as a PBMParameter. A crafted message can_x000D_ contain a parameter of a different type, which is then dereferenced as an_x000D_ invalid pointer._x000D_
_x000D_ Impact summary: A remote, unauthenticated attacker can crash an application_x000D_ acting as a CMP server that accepts PBM-protected messages, or a CMP client_x000D_ talking to a malicious or intercepted CMP server, resulting in a Denial of_x000D_ Service._x000D_
_x000D_ CWE: CWE-476: NULL Pointer Dereference_x000D_
_x000D_ Description: When verifying the password-based MAC protection of a CMP_x000D_ message, OpenSSL library reads the protectionAlg algorithm parameter with_x000D_ X509_ALGOR_get0(), which returns both the parameter type and its value_x000D_ pointer. The value is then cast to an ASN1_STRING and treated as the_x000D_ expected PBMParameter after only checking that pointer is not NULL. The_x000D_ parameter type returned by X509_ALGOR_get0() was never consulted._x000D_
_x000D_ This happens during protection verification, before any MAC is computed, so_x000D_ no knowledge of the PBM shared secret is required; the only precondition is_x000D_ that PBM verification is reachable. On the server side this is reached from_x000D_ OSSL_CMP_SRV_process_request() for any application that stands up a CMP_x000D_ server accepting PBM-protected messages, and on the client side from CMP_x000D_ response validation against a malicious or on-path (MITM) server. The_x000D_ reliable consequence is a denial of service; there is no memory disclosure,_x000D_ no controlled memory write, and no path to code execution. CMP is a_x000D_ specialized feature that an application must explicitly enable._x000D_
_x000D_ FIPS impact: no_x000D_ As the CMP code lives outside the FIPS module boundary, no FIPS modules_x000D_ are affected by this CVE.(CVE-2026-63076)

Issue summary: Receiving a DTLS record for a future epoch while a handshake_x000D_ is in progress causes OpenSSL to buffer far more memory than the record_x000D_ itself requires._x000D_
_x000D_ Impact summary: A peer can use a small amount of network traffic to make an_x000D_ OpenSSL DTLS endpoint retain a disproportionately large amount of memory,_x000D_ which may lead to a Denial of Service._x000D_
_x000D_ CWE: CWE-405: Asymmetric Resource Consumption (Amplification)_x000D_
_x000D_ Description: While a DTLS handshake is in progress, a peer may legitimately_x000D_ have already moved on to the next epoch (for example, having sent its_x000D_ ChangeCipherSpec and Finished messages) before the local endpoint has_x000D_ processed the same transition, typically because of reordering on the_x000D_ underlying UDP transport. OpenSSL buffers such early records so that they_x000D_ can be processed once the local endpoint catches up._x000D_
_x000D_ Buffering a record currently retains the entire read buffer it arrived in,_x000D_ which is sized to hold the largest possible DTLS record (around 16_x000D_ kilobytes), rather than just the bytes that make up the record itself. Up_x000D_ to 100 such records may be buffered per connection. As a result, a peer_x000D_ that sends a stream of small forged records claiming to belong to the next_x000D_ epoch can cause an OpenSSL DTLS endpoint to retain around 1.7 megabytes of_x000D_ memory, despite sending only a small fraction of that amount of data over_x000D_ the network._x000D_
_x000D_ An attacker therefore gains a memory amplification factor of around 1200,_x000D_ and can multiply the effect across as many associations as it is able to_x000D_ open, making this a remote memory exhaustion Denial of Service risk for_x000D_ DTLS servers. Since the memory retained per connection remains bounded,_x000D_ and any limit an application already places on the number of concurrent_x000D_ associations also bounds the total exposure, this issue has been assessed_x000D_ as Low severity._x000D_
_x000D_ FIPS impact: no_x000D_
_x000D_ No FIPS modules are affected by this issue as the affected code is outside_x000D_ the OpenSSL FIPS module boundary._x000D_
_x000D_ OpenSSL 4.0, 3.6, 3.5, 3.4, 3.0, 1.1.1 and 1.0.2 are vulnerable to this_x000D_ issue._x000D_
_x000D_ OpenSSL 4.0 users should upgrade to OpenSSL 4.0.2._x000D_ OpenSSL 3.6 users should upgrade to OpenSSL 3.6.4._x000D_ OpenSSL 3.5 users should upgrade to OpenSSL 3.5.8._x000D_ OpenSSL 3.4 users should upgrade to OpenSSL 3.4.7._x000D_ OpenSSL 3.0 users should upgrade to OpenSSL 3.0.22._x000D_
_x000D_ Premium support customers only:_x000D_ OpenSSL 1.1.1 users should upgrade to OpenSSL 1.1.1zi_x000D_ OpenSSL 1.0.2 users should upgrade to OpenSSL 1.0.2zr_x000D_
_x000D_ This issue was reported on 18 May 2026 by Amazon Web Services._x000D_ The fix has been developed by Matt Caswell._x000D_
_x000D_
-- cut (non-publishing metadata for internal use) --_x000D_ Reported by: Amazon Web Services_x000D_ Fixed by: Matt Caswell(CVE-2026-54874)

Issue summary: The OpenSSL Certificate Management Protocol (CMP) caches_x000D_ additional certificates (extraCerts) sent in a CMP message, but never expunges_x000D_ them (for instance if they are invalid). If a server reuses an OSSL_CMP_CTX_x000D_ frequently, this cache of extraCerts may grow unboundedly, and a malicious_x000D_ client may flood a CMP server with requests driving this growth._x000D_
_x000D_ Impact summary: Users utilizing a CMP server that reuses a single OSSL_CMP_CTX_x000D_ for the lifetime of a server process may observe unbounded memory growth in the_x000D_ event a malicious client repeatedly sends requests containing unique extra_x000D_ certificates, which may lead to OOM conditions._x000D_
_x000D_ CWE: CWE-770: Allocation of Resources Without Limits or Throttling_x000D_
_x000D_ Description: If a remote user sends CMP messages to a server with a list of_x000D_ extraCerts and the message is rejected, the extraCerts from the message remains_x000D_ in the server contexts untrusted certificate stack. This exposes servers with_x000D_ long lived ctx objects to Denial of Service attacks in which an attacker sends_x000D_ messages intending to be rejected with a large list of additional certificates_x000D_ repeatedly, forcing the server to store them indefinitely._x000D_
_x000D_ The issue was fixed by removing the added extra certs if the message is_x000D_ rejected, using the same method as when the context is configured to not do_x000D_ caching at all._x000D_
_x000D_ FIPS impact: no_x000D_ As the CMP code lives outside the FIPS module boundary, no FIPS_x000D_ modules are affected by this CVE.(CVE-2026-63074)

Issue summary: OpenSSL CMS decryption sizes the key-unwrap output buffer based_x000D_ on querying the unwrapped key size, but the AES-WRAP-PAD unwrap primitive_x000D_ can write and cleanse more bytes than that query reports, causing an 8-byte_x000D_ out-of-bounds heap write._x000D_
_x000D_ Impact summary: An attacker who supplies a crafted CMS message can trigger a_x000D_ deterministic 8-byte out-of-bounds heap write when the victim decrypts it_x000D_ with CMS_decrypt(), corrupting the heap and typically resulting in a Denial_x000D_ of Service._x000D_
_x000D_ CWE: CWE-787: Out-of-bounds Write_x000D_
_x000D_ Description: The key-wrap OID is potentially attacker-controlled on the wire._x000D_ CMS unwrapping allows both id-aesNNN-wrap-pad and id-aesNNN-wrap ciphers._x000D_ An attacker can take a legitimate message and change a single OID byte to_x000D_ select the padded variant while leaving the message otherwise valid. Since_x000D_ the unwrap key is derived from the recipient's private operation (ECDH key_x000D_ agreement or ML-KEM decapsulation), the RFC 5649 integrity check cannot_x000D_ pass, and the decryption fails with integrity failure._x000D_
_x000D_ The write is a fixed-size (8-byte), fixed-value (zero) heap overflow_x000D_ immediately past the allocation, requires no special configuration, and is_x000D_ reachable from the public CMS_decrypt() function. The consequence is_x000D_ a heap corruption leading to a Denial of Service. The fix in the CMS code_x000D_ sizes the unwrap output buffer for the worst case so a failed unwrap cannot_x000D_ write past the allocation._x000D_
_x000D_ FIPS impact: no_x000D_
_x000D_ As the CMS code lives outside the FIPS module boundary, no FIPS_x000D_ modules are affected by this CVE.(CVE-2026-63072)

Tenable has extracted the preceding description block directly from the EulerOS openssl security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

Solution

Update the affected openssl packages.

See Also

http://www.nessus.org/u?9dc3b3c8

Plugin Details

Severity: Critical

ID: 383292

File Name: EulerOS_SA-2026-5194.nasl

Version: 1.1

Type: Local

Published: 11/19/2026

Updated: 11/19/2026

Supported Sensors: Nessus

Risk Information

VPR

Risk Factor: Medium

Score: 6

Percentile: 96

CVSS v2

Risk Factor: Critical

Base Score: 10

Temporal Score: 7.4

Vector: CVSS2#AV:N/AC:L/Au:N/C:C/I:C/A:C

CVSS Score Source: CVE-2026-75803

CVSS v3

Risk Factor: Critical

Base Score: 9.1

Temporal Score: 7.9

Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Temporal Vector: CVSS:3.0/E:U/RL:O/RC:C

Vulnerability Information

CPE: cpe:/o:huawei:euleros:2.0, p-cpe:/a:huawei:euleros:openssl-devel, p-cpe:/a:huawei:euleros:openssl-help, p-cpe:/a:huawei:euleros:openssl-libs, p-cpe:/a:huawei:euleros:openssl-perl, p-cpe:/a:huawei:euleros:openssl

Required KB Items: Host/local_checks_enabled, Host/cpu, Host/EulerOS/release, Host/EulerOS/rpm-list, Host/EulerOS/sp

Excluded KB Items: Host/EulerOS/uvp_version

Exploit Ease: No known exploits are available

Patch Publication Date: 11/19/2026

Vulnerability Publication Date: 8/5/2026

Reference Information

CVE: CVE-2026-54874, CVE-2026-63072, CVE-2026-63074, CVE-2026-63076, CVE-2026-75803