OpenSSL 3.4.0 < 3.4.8 Multiple Vulnerabilities

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

include('compat.inc');

if (description)
{
  script_id(352191);
  script_version("1.1");
  script_set_attribute(attribute:"plugin_modification_date", value:"2026/09/30");

  script_cve_id(
    "CVE-2026-35189",
    "CVE-2026-42772",
    "CVE-2026-54872",
    "CVE-2026-54873",
    "CVE-2026-54875",
    "CVE-2026-72897",
    "CVE-2026-75804",
    "CVE-2026-75805",
    "CVE-2026-75806",
    "CVE-2026-77696",
    "CVE-2026-84782",
    "CVE-2026-84784"
  );

  script_name(english:"OpenSSL 3.4.0 < 3.4.8 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.4.8. It is, therefore, affected by multiple
vulnerabilities as referenced in the 3.4.8 advisory.

  - 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 (returning WANT_WRITE) if the underlying transport temporarily cannot accept more
    data. While such a write is suspended, the DTLS retransmission timer may independently fire and ask the
    retransmission logic to resend an earlier, already-acknowledged-as-sent message from its retransmit queue.
    The retransmission logic reused the same internal buffer and position tracking as the message that was
    still being written, without resetting the position back to the start of the message being retransmitted.
    As a result the retransmission was read starting from wherever the suspended write had left off, producing
    a mislabelled message whose body was leftover bytes from the other, larger message still in flight -
    content that was never meant to be sent at that point, and which could run past the end of the allocated
    buffer. Separately, even when the retransmission is positioned correctly, allowing it to run to completion
    while another write is suspended overwrites the same shared bookkeeping that the suspended write depends
    on to resume. When the application later resumes the suspended write (via a subsequent SSL_read(),
    SSL_write(), SSL_accept(), or SSL_connect() call), it finds that bookkeeping in a state inconsistent with
    the message and aborts the process in a debugging build. The fix resets the retransmission's read position
    to the start of the message before resending, and skips retransmission entirely whenever a handshake write
    is still suspended, deferring to the next call that resumes it instead. FIPS impact: no The affected code
    is outside the FIPS module boundary. (CVE-2026-84782)

  - 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 receiving side during a normal TLS handshake. This may be enough to crash the
    client or server, if multiple concurrent connections lead to similarly large memory allocations. The fix
    postpones processing of the CRL distribution points extensions in certificates to the time when the
    processed value is required for CRL processing. This avoids keeping large memory allocations for a long
    time when such certificates are received. FIPS impact: no The affected code is outside the FIPS module
    boundary. (CVE-2026-35189)

  - 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 it optimizes for append operations (at the end of the list), it falls back to a
    head-to-tail linear search for any fragment that does not immediately follow the current `tail`. By
    manipulating the sequence of offsets, an attacker can force the server to perform O(n^2) operations,
    consuming excessive CPU time for the QUIC process. FIPS impact: no The FIPS module is not affected as the
    QUIC implementation is outside of the OpenSSL FIPS module boundary. (CVE-2026-42772)

  - 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 secret scalar with non-constant-time BIGNUM operations, so the time
    taken depends on the value of the secret scalar derived from the ECDSA and SM2 nonce. The leak is very
    small; observing it requires a large number of measurements. The effect is largest for curves whose group
    order lies on a machine-word boundary, such as brainpoolP384r1. Applications using ECDSA signing over the
    Brainpool and other generic prime curves, and SM2 signing on platforms that use the generic
    implementation, are vulnerable to this issue. The NIST curves P-256, P-384 and P-521 use dedicated
    constant-time implementations and are not affected. FIPS Impact: no The FIPS modules are not affected: the
    approved NIST curves used in the FIPS provider have dedicated constant-time implementations and do not use
    the affected code path. (CVE-2026-54872)

  - 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 buffer provided by the local receiving application. The QUIC stack releases a reference
    to the packet buffer only after the data are copied to the application buffer. This design is more
    efficient for legitimate data transfers but enables an attacker to allocate a lot more memory than
    actually required by the data kept in the receiving stream buffer. To mitigate the vulnerability, the QUIC
    stack now calculates and monitors memory overhead for every stream. The memory overhead for a single
    stream frame is calculated as a difference between the size of the whole packet that carries the stream
    frame and the size of the stream frame itself. The memory overhead for a single stream frame is added to
    the total (cumulative) memory overhead QUIC stack keeps for each stream. Once the cumulative memory
    overhead exceeds 64kB, the QUIC stack moves the stream frame data from the packet buffer to the stream
    buffer, starting with the next packet received. FIPS impact: no The FIPS module is not affected as the
    QUIC implementation is outside of the OpenSSL FIPS module boundary. (CVE-2026-54873)

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/openssl/commit/00646e5085a0d12d29e0d2f9b9bc5f7111a50922
  script_set_attribute(attribute:"see_also", value:"http://www.nessus.org/u?e0435398");
  # https://github.com/openssl/openssl/commit/3ea6213e050e938ecbbf8c4eff32bec2736780eb
  script_set_attribute(attribute:"see_also", value:"http://www.nessus.org/u?f40ddbde");
  # https://github.com/openssl/openssl/commit/3f01bbc28f7e08211fcdc797fd43816504f94257
  script_set_attribute(attribute:"see_also", value:"http://www.nessus.org/u?75e4e627");
  # https://github.com/openssl/openssl/commit/419f5cb519721dceed393dbc524d79e487c72e64
  script_set_attribute(attribute:"see_also", value:"http://www.nessus.org/u?a6b88086");
  # https://github.com/openssl/openssl/commit/5af82fefbaf2b5fec2fc0e1d87f112844902f01d
  script_set_attribute(attribute:"see_also", value:"http://www.nessus.org/u?fc1ca82b");
  # https://github.com/openssl/openssl/commit/7d83bc7764999dfd91b83b4f0815b45390422afd
  script_set_attribute(attribute:"see_also", value:"http://www.nessus.org/u?6865f86d");
  # https://github.com/openssl/openssl/commit/9a30fe0fba195c14e5b87bf93c0d0fdb70373806
  script_set_attribute(attribute:"see_also", value:"http://www.nessus.org/u?c086f679");
  # https://github.com/openssl/openssl/commit/9f6b34422af7eb5dac61322e33dac1ae989fa628
  script_set_attribute(attribute:"see_also", value:"http://www.nessus.org/u?05b7e7f1");
  # https://github.com/openssl/openssl/commit/abf02872a4b71767ecc72293424420f5b009190f
  script_set_attribute(attribute:"see_also", value:"http://www.nessus.org/u?3dec9b7d");
  # https://github.com/openssl/openssl/commit/c72ae182cac17a82e4246c6ecd4e9c4ec3586ec9
  script_set_attribute(attribute:"see_also", value:"http://www.nessus.org/u?40e6f485");
  # https://github.com/openssl/openssl/commit/eb2becc0a4baea7f3050a247834d0e5c2ebe1773
  script_set_attribute(attribute:"see_also", value:"http://www.nessus.org/u?01ba812d");
  # https://github.com/openssl/openssl/commit/f9eaecf5bdd6692da052bc65b0332af2a938ac03
  script_set_attribute(attribute:"see_also", value:"http://www.nessus.org/u?4659fb53");
  script_set_attribute(attribute:"see_also", value:"https://openssl-library.org/news/secadv/20260929.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-35189");
  script_set_attribute(attribute:"see_also", value:"https://www.cve.org/CVERecord?id=CVE-2026-42772");
  script_set_attribute(attribute:"see_also", value:"https://www.cve.org/CVERecord?id=CVE-2026-54872");
  script_set_attribute(attribute:"see_also", value:"https://www.cve.org/CVERecord?id=CVE-2026-54873");
  script_set_attribute(attribute:"see_also", value:"https://www.cve.org/CVERecord?id=CVE-2026-54875");
  script_set_attribute(attribute:"see_also", value:"https://www.cve.org/CVERecord?id=CVE-2026-72897");
  script_set_attribute(attribute:"see_also", value:"https://www.cve.org/CVERecord?id=CVE-2026-75804");
  script_set_attribute(attribute:"see_also", value:"https://www.cve.org/CVERecord?id=CVE-2026-75805");
  script_set_attribute(attribute:"see_also", value:"https://www.cve.org/CVERecord?id=CVE-2026-75806");
  script_set_attribute(attribute:"see_also", value:"https://www.cve.org/CVERecord?id=CVE-2026-77696");
  script_set_attribute(attribute:"see_also", value:"https://www.cve.org/CVERecord?id=CVE-2026-84782");
  script_set_attribute(attribute:"see_also", value:"https://www.cve.org/CVERecord?id=CVE-2026-84784");
  script_set_attribute(attribute:"solution", value:
"Upgrade to OpenSSL version 3.4.8 or later.");
  script_set_attribute(attribute:"agent", value:"all");
  script_set_cvss_base_vector("CVSS2#AV:N/AC:L/Au:N/C:P/I:N/A:C");
  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:L/I:N/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-84782");

  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/09/29");
  script_set_attribute(attribute:"patch_publication_date", value:"2026/09/29");
  script_set_attribute(attribute:"plugin_publication_date", value:"2026/09/30");

  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.4.0', 'fixed_version' : '3.4.8' }
];

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