OpenSSL 3.0.0 < 3.0.21 Multiple Vulnerabilities

#%NASL_MIN_LEVEL 80900
##
# (C) Tenable, Inc.
##

include('compat.inc');

if (description)
{
  script_id(320142);
  script_version("1.2");
  script_set_attribute(attribute:"plugin_modification_date", value:"2026/06/10");

  script_cve_id(
    "CVE-2026-7383",
    "CVE-2026-9076",
    "CVE-2026-34180",
    "CVE-2026-34182",
    "CVE-2026-42766",
    "CVE-2026-42767",
    "CVE-2026-42770",
    "CVE-2026-45445",
    "CVE-2026-45446",
    "CVE-2026-45447"
  );

  script_name(english:"OpenSSL 3.0.0 < 3.0.21 Multiple Vulnerabilities");

  script_set_attribute(attribute:"synopsis", value:
"The remote service is affected by multiple vulnerabilities.");
  script_set_attribute(attribute:"description", value:
"The version of OpenSSL installed on the remote host is prior to 3.0.21. It is, therefore, affected by multiple
vulnerabilities as referenced in the 3.0.21 advisory.

  - Issue summary: An attacker-controlled CMP (Certificate Management Protocol) server could trigger a NULL
    pointer dereference in a CMP client application. Impact summary: A NULL pointer dereference causes a crash
    of the application and a Denial of Service. An attacker controlling a CMP server (or acting as a man-in-
    the-middle) could craft a CMP response containing a CRMF (Certificate Request Message Format)
    CertRepMessage with an EncryptedValue structure where the symmAlg field has an algorithm OID but no
    parameters field. When the OpenSSL CMP client processes this response, the NULL dereference occurs,
    causing a crash of the CMP client. Applications that process untrusted CMP/CRMF messages may be affected.
    The FIPS modules in 4.0, 3.6, 3.5, 3.4, and 3.0 are not affected by this issue, as the affected code is
    outside the OpenSSL FIPS module boundary. (CVE-2026-42767)

  - 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 worst case (UNIVERSALSTRING at 2^30 characters) the size
    wraps to zero, OPENSSL_malloc(1) is called, and the subsequent character copy writes several gigabytes
    past the one-byte allocation. X.509 certificate processing routes through ASN1_STRING_set_by_NID(), whose
    DIRSTRING_TYPE mask excludes UNIVERSALSTRING and whose per-NID size limits cap the input length; no
    network protocol or certificate-handling path in OpenSSL exercises the overflow. Triggering the bug
    requires an application that calls ASN1_mbstring_copy() or ASN1_mbstring_ncopy() directly, or registers a
    custom string type via ASN1_STRING_TABLE_add(), with attacker-controlled input on the order of half a
    gigabyte or more. For these reasons this issue was assigned Low severity. The FIPS modules in 4.0, 3.6,
    3.5, 3.4 and 3.0 are not affected by this issue, as the affected code is outside the OpenSSL FIPS module
    boundary. (CVE-2026-7383)

  - 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 the wrapped key length from the message. There is a minimum length check based
    on the block length of the wrapping cipher. However the cipher is selected from an OID carried in the
    attacker's PWRI keyEncryptionAlgorithm with no requirement that the cipher be a block cipher. When an
    attacker selects a stream-mode cipher the guard will be ineffective and the allocated buffer containing
    the unwrapped key can be too small to fit the check-bytes specified in the RFC and a buffer over-read can
    happen. Applications calling CMS_decrypt() or CMS_decrypt_set1_password() (equivalently openssl cms
    -decrypt -pwri_password ...) on untrusted CMS data are vulnerable to this issue. No password knowledge is
    required: the over-read happens during the unwrap attempt before any authentication succeeds. The over-
    read is limited to a few bytes and is not written to output, so there is no information disclosure.
    Triggering a crash requires the allocation to border unmapped memory, which is unlikely with the normal
    allocator. The FIPS modules are not affected by this issue. (CVE-2026-9076)

  - Issue summary: A specially crafted PKCS#7 or S/MIME signed message could trigger a use-after-free during
    PKCS#7 signature verification. Impact summary: A use-after-free may result in process crashes, heap
    corruption, or potentially remote code execution. When processing a PKCS#7 or S/MIME signed message, if
    the SignedData digestAlgorithms field is present as an empty ASN.1 SET, OpenSSL may incorrectly free a
    caller-owned BIO during PKCS7_verify(). A subsequent use of the BIO by the calling application results in
    a use-after-free condition. In the common case this occurs when the application later calls BIO_free() on
    the BIO originally passed to PKCS7_verify(). Depending on allocator behavior and application-specific BIO
    usage patterns, this may result in a crash or other memory corruption. In some application contexts this
    may potentially be exploitable for remote code execution. Applications that process PKCS#7 or S/MIME
    signed messages using OpenSSL PKCS#7 APIs may be affected. Applications using the CMS APIs for this
    processing are not affected. The FIPS modules in 4.0, 3.6, 3.5, 3.4, and 3.0 are not affected by this
    issue, as the affected code is outside the OpenSSL FIPS module boundary. (CVE-2026-45447)

  - Issue summary: The implementations of AES-SIV (RFC 5297) and AES-GCM-SIV (RFC 8452) mishandle the
    authentication of AAD (Additional Authenticated Data) with an empty ciphertext allowing a forgery of such
    messages. Impact summary: An attacker can forge empty messages with arbitrary AAD to the victim's
    application using these ciphers. AES-SIV (RFC 5297) and AES-GCM-SIV (RFC 8452) are nonce-misuse-resistant
    AEAD modes: they accept a key, nonce, optional AAD (bytes that are authenticated but not encrypted), and
    plaintext, and produces ciphertext plus a 16-byte tag. On decrypt, `EVP_DecryptFinal_ex()` is documented
    to return success only if the tag is verified succesfully. In OpenSSL's provider implementation of these
    ciphers, the expected tag is computed only when decryption function is invoked with non-empty data. If the
    caller supplies AAD and then calls `EVP_DecryptFinal_ex()` without invocation of the ciphertext update,
    which can happen when the received ciphertext length is zero, the tag is never recalculated and still
    holds its all-zeros value. When AES-GCM-SIV is used, an attacker who sends arbitrary AAD, empty
    ciphertext, and all-zeros tag passes authentication under any key they do not know, single-shot. When AES-
    SIV is used, for mounting the attack it's necessary for the application to reuse the decryption context
    without resetting the key. AES-SIV is implemented since OpenSSL 3.0. AES-GCM-SIV is implemented since
    OpenSSL 3.2. No protocols implemented in OpenSSL itself (TLS/CMS/PKCS7/HPKE/QUIC) support either AES-GCM-
    SIV or AES-SIV. To mount an attack, the applications must implement their own protocol and use the EVP
    interface. Also they must skip the ciphertext update when a message with an empty ciphertext arrives. The
    FIPS modules in 4.0, 3.6, 3.5, 3.4, and 3.0 are not affected by this issue, as these algorithms are not
    FIPS approved and the affected code is outside the OpenSSL FIPS module boundary. (CVE-2026-45446)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version
number.");
  # https://github.com/openssl/security/commit/03c1f4d45fb963aee7d5833390c507cd290182bc
  script_set_attribute(attribute:"see_also", value:"http://www.nessus.org/u?a53718d0");
  # https://github.com/openssl/security/commit/323f0b6e7d530a4cb4336d50c88cb70f3ac2a451
  script_set_attribute(attribute:"see_also", value:"http://www.nessus.org/u?ecd90bca");
  # https://github.com/openssl/security/commit/3ff64913615d648cfbb6a6f1cf5529ae7ea829d7
  script_set_attribute(attribute:"see_also", value:"http://www.nessus.org/u?9e18ffb8");
  # https://github.com/openssl/security/commit/61a86a8cd73546c9fea916f3d304c1293e05c046
  script_set_attribute(attribute:"see_also", value:"http://www.nessus.org/u?0c8bd0f0");
  # https://github.com/openssl/security/commit/71e2a5d263518cf5866043bd60ee4994d59e53a3
  script_set_attribute(attribute:"see_also", value:"http://www.nessus.org/u?c40bd025");
  # https://github.com/openssl/security/commit/7fbfde7677ed8808828bf00ff01c937ca04bdda2
  script_set_attribute(attribute:"see_also", value:"http://www.nessus.org/u?772401e3");
  # https://github.com/openssl/security/commit/9dfd688ad2290fc5075cacbc9bf0c9a93eefed54
  script_set_attribute(attribute:"see_also", value:"http://www.nessus.org/u?b70e0b9e");
  # https://github.com/openssl/security/commit/bd17511070fb39a67bfa19682affb765e706a974
  script_set_attribute(attribute:"see_also", value:"http://www.nessus.org/u?50d8a95f");
  # https://github.com/openssl/security/commit/cbe418ae978539cf14a398a207dba834c0e93e83
  script_set_attribute(attribute:"see_also", value:"http://www.nessus.org/u?e19276bf");
  # https://github.com/openssl/security/commit/eecbe330977e8d023aae1ca2d9bdbe983ef3fdc6
  script_set_attribute(attribute:"see_also", value:"http://www.nessus.org/u?2723d0e1");
  script_set_attribute(attribute:"see_also", value:"https://openssl-library.org/news/secadv/20260609.txt");
  # https://openssl-library.org/policies/general/security-policy/index.html
  script_set_attribute(attribute:"see_also", value:"http://www.nessus.org/u?eac4598c");
  script_set_attribute(attribute:"see_also", value:"https://www.cve.org/CVERecord?id=CVE-2026-34180");
  script_set_attribute(attribute:"see_also", value:"https://www.cve.org/CVERecord?id=CVE-2026-34182");
  script_set_attribute(attribute:"see_also", value:"https://www.cve.org/CVERecord?id=CVE-2026-42766");
  script_set_attribute(attribute:"see_also", value:"https://www.cve.org/CVERecord?id=CVE-2026-42767");
  script_set_attribute(attribute:"see_also", value:"https://www.cve.org/CVERecord?id=CVE-2026-42770");
  script_set_attribute(attribute:"see_also", value:"https://www.cve.org/CVERecord?id=CVE-2026-45445");
  script_set_attribute(attribute:"see_also", value:"https://www.cve.org/CVERecord?id=CVE-2026-45446");
  script_set_attribute(attribute:"see_also", value:"https://www.cve.org/CVERecord?id=CVE-2026-45447");
  script_set_attribute(attribute:"see_also", value:"https://www.cve.org/CVERecord?id=CVE-2026-7383");
  script_set_attribute(attribute:"see_also", value:"https://www.cve.org/CVERecord?id=CVE-2026-9076");
  script_set_attribute(attribute:"solution", value:
"Upgrade to OpenSSL version 3.0.21 or later.");
  script_set_attribute(attribute:"agent", value:"all");
  script_set_cvss_base_vector("CVSS2#AV:N/AC:M/Au:N/C:N/I:N/A:P");
  script_set_cvss_temporal_vector("CVSS2#E:U/RL:OF/RC:C");
  script_set_cvss3_base_vector("CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H");
  script_set_cvss3_temporal_vector("CVSS:3.0/E:U/RL:O/RC:C");
  script_set_attribute(attribute:"cvss_score_source", value:"CVE-2026-42767");
  script_set_attribute(attribute:"cvss3_score_source", value:"CVE-2026-45447");

  script_set_attribute(attribute:"exploitability_ease", value:"No known exploits are available");
  script_set_attribute(attribute:"exploit_available", value:"false");

  script_set_attribute(attribute:"vuln_publication_date", value:"2026/06/09");
  script_set_attribute(attribute:"patch_publication_date", value:"2026/06/09");
  script_set_attribute(attribute:"plugin_publication_date", value:"2026/06/09");

  script_set_attribute(attribute:"plugin_type", value:"combined");
  script_set_attribute(attribute:"cpe", value:"cpe:/a:openssl:openssl");
  script_set_attribute(attribute:"generated_plugin", value:"current");
  script_set_attribute(attribute:"thorough_tests", value:"true");
  script_end_attributes();

  script_category(ACT_GATHER_INFO);
  script_family(english:"Web Servers");

  script_copyright(english:"This script is Copyright (C) 2026 and is owned by Tenable, Inc. or an Affiliate thereof.");

  script_dependencies("openssl_version.nasl", "openssl_nix_installed.nbin", "openssl_win_installed.nbin");
  script_require_keys("installed_sw/OpenSSL");

  exit(0);
}

include('vcf.inc');
include('vcf_extras_openssl.inc');

var app_info = vcf::combined_get_app_info(app:'OpenSSL');

vcf::check_all_backporting(app_info:app_info);

var constraints = [
  { 'min_version' : '3.0.0', 'fixed_version' : '3.0.21' }
];

vcf::openssl::check_version_and_report(
    app_info:app_info,
    constraints:constraints,
    severity:SECURITY_WARNING
);