OpenSSL 1.1.1 < 1.1.1zi Multiple Vulnerabilities

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

include('compat.inc');

if (description)
{
  script_id(339486);
  script_version("1.1");
  script_set_attribute(attribute:"plugin_modification_date", value:"2026/08/25");

  script_cve_id("CVE-2026-54874", "CVE-2026-63072");

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

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

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

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/20260825.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-54874");
  script_set_attribute(attribute:"see_also", value:"https://www.cve.org/CVERecord?id=CVE-2026-63072");
  script_set_attribute(attribute:"solution", value:
"Upgrade to OpenSSL version 1.1.1zi or later.");
  script_set_attribute(attribute:"agent", value:"all");
  script_set_cvss_base_vector("CVSS2#AV:N/AC:L/Au:N/C:N/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:N/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-63072");
  script_set_attribute(attribute:"cvss3_score_source", value:"CVE-2026-54874");

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

  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.1zi' }
];

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