OpenSSL 1.1.1 < 1.1.1zj Multiple Vulnerabilities

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

include('compat.inc');

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

  script_cve_id(
    "CVE-2026-35189",
    "CVE-2026-54872",
    "CVE-2026-75806",
    "CVE-2026-77696",
    "CVE-2026-84782"
  );

  script_name(english:"OpenSSL 1.1.1 < 1.1.1zj 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 1.1.1zj. It is, therefore, affected by multiple
vulnerabilities as referenced in the 1.1.1zj 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 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: An established DTLS 1.2 association using an AEAD cipher suite can be terminated by a
    single unauthenticated datagram whose encrypted fragment is shorter than the mandatory explicit IV and
    authentication tag overhead. Impact summary: An attacker who can send a datagram that is routed to an
    existing DTLS 1.2 association can tear that association down without knowing any key material. This is a
    Denial of Service limited to the targeted association. There is no memory safety or confidentiality
    impact. CWE: CWE-1284: Improper Validation of Specified Quantity in Input Description: In TLS 1.2 and DTLS
    1.2 every record protected by an AEAD cipher suite carries an explicit IV followed by the ciphertext and
    an authentication tag. When decrypting such a record the record layer passed the record length to the
    cipher implementation before checking that the record was long enough to contain the explicit IV and the
    tag. For a record shorter than that overhead the cipher implementation rejected the impossible length, and
    the record layer treated this as an internal failure and raised a fatal internal_error alert instead of
    treating the record as one that failed authentication. In TLS 1.2 the same record causes a fatal
    internal_error alert instead of the expected bad_record_mac alert. Since any undecryptable record already
    terminates a TLS connection, this is a protocol conformance issue rather than a security issue in TLS. The
    fix validates the record length against the explicit IV and tag length before any AEAD processing, so that
    TLS reports bad_record_mac and DTLS silently discards the record. FIPS impact: no The affected code is
    outside the FIPS module boundary. (CVE-2026-75806)

  - Issue summary: SM2 signature generation uses non-constant-time arithmetic on secret values, forming a
    timing side-channel. Impact summary: An attacker able to measure SM2 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: SM2 signature generation computes the signature value using variable-time BIGNUM operations
    on the secret nonce and the private key, so the time taken to produce an SM2 signature depends on these
    secret values, forming a timing side-channel. Applications performing SM2 signature generation are
    affected on all platforms. FIPS Impact: no SM2 is not a FIPS algorithm. (CVE-2026-77696)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version
number.");
  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-54872");
  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:"solution", value:
"Upgrade to OpenSSL version 1.1.1zj 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' : '1.1.1', 'fixed_version' : '1.1.1zj' }
];

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