OpenSSL 1.1.1 < 1.1.1zg Multiple Vulnerabilities

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

include('compat.inc');

if (description)
{
  script_id(305204);
  script_version("1.3");
  script_set_attribute(attribute:"plugin_modification_date", value:"2026/04/27");

  script_cve_id(
    "CVE-2026-28387",
    "CVE-2026-28388",
    "CVE-2026-28389",
    "CVE-2026-28390"
  );
  script_xref(name:"IAVA", value:"2026-A-0308");

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

  - Issue summary: An uncommon configuration of clients performing DANE TLSA-based server authentication, when
    paired with uncommon server DANE TLSA records, may result in a use-after-free and/or double-free on the
    client side.  Impact summary: A use after free can have a range of potential consequences such as the
    corruption of valid data, crashes or execution of arbitrary code.  However, the issue only affects clients
    that make use of TLSA records with both the PKIX-TA(0/PKIX-EE(1) certificate usages and the DANE-TA(2)
    certificate usage.  By far the most common deployment of DANE is in SMTP MTAs for which RFC7672 recommends
    that clients treat as 'unusable' any TLSA records that have the PKIX certificate usages.  These SMTP (or
    other similar) clients are not vulnerable to this issue.  Conversely, any clients that support only the
    PKIX usages, and ignore the DANE-TA(2) usage are also not vulnerable.  The client would also need to be
    communicating with a server that publishes a TLSA RRset with both types of TLSA records.  No FIPS modules
    are affected by this issue, the problem code is outside the FIPS module boundary. Fixed in OpenSSL 1.1.1zg
    (Affected since 1.1.1). (CVE-2026-28387)

  - Issue summary: During processing of a crafted CMS EnvelopedData message with KeyTransportRecipientInfo a
    NULL pointer dereference can happen.  Impact summary: Applications that process attacker-controlled CMS
    data may crash before authentication or cryptographic operations occur resulting in Denial of Service.
    When a CMS EnvelopedData message that uses KeyTransportRecipientInfo with RSA-OAEP encryption is
    processed, the optional parameters field of RSA-OAEP SourceFunc algorithm identifier is examined without
    checking for its presence. This results in a NULL pointer dereference if the field is missing.
    Applications and services that call CMS_decrypt() on untrusted input (e.g., S/MIME processing or CMS-based
    protocols) are vulnerable.  The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue,
    as the affected code is outside the OpenSSL FIPS module boundary. Fixed in OpenSSL 1.1.1zg (Affected since
    1.1.1). (CVE-2026-28390)

  - Issue summary: During processing of a crafted CMS EnvelopedData message with KeyAgreeRecipientInfo a NULL
    pointer dereference can happen.  Impact summary: Applications that process attacker-controlled CMS data
    may crash before authentication or cryptographic operations occur resulting in Denial of Service.  When a
    CMS EnvelopedData message that uses KeyAgreeRecipientInfo is processed, the optional parameters field of
    KeyEncryptionAlgorithmIdentifier is examined without checking for its presence. This results in a NULL
    pointer dereference if the field is missing.  Applications and services that call CMS_decrypt() on
    untrusted input (e.g., S/MIME processing or CMS-based protocols) are vulnerable.  The FIPS modules in 3.6,
    3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the affected code is outside the OpenSSL FIPS
    module boundary. Fixed in OpenSSL 1.1.1zg (Affected since 1.1.1). (CVE-2026-28389)

  - Issue summary: When a delta CRL that contains a Delta CRL Indicator extension is processed a NULL pointer
    dereference might happen if the required CRL Number extension is missing.  Impact summary: A NULL pointer
    dereference can trigger a crash which leads to a Denial of Service for an application.  When CRL
    processing and delta CRL processing is enabled during X.509 certificate verification, the delta CRL
    processing does not check whether the CRL Number extension is NULL before dereferencing it. When a
    malformed delta CRL file is being processed, this parameter can be NULL, causing a NULL pointer
    dereference.  Exploiting this issue requires the X509_V_FLAG_USE_DELTAS flag to be enabled in the
    verification context, the certificate being verified to contain a freshestCRL extension or the base CRL to
    have the EXFLAG_FRESHEST flag set, and an attacker to provide a malformed CRL to an application that
    processes it.  The vulnerability is limited to Denial of Service and cannot be escalated to achieve code
    execution or memory disclosure. For that reason the issue was assessed as Low severity according to our
    Security Policy.  The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the
    affected code is outside the OpenSSL FIPS module boundary. Fixed in OpenSSL 1.1.1zg (Affected since
    1.1.1). (CVE-2026-28388)

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/20260407.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-28387");
  script_set_attribute(attribute:"see_also", value:"https://www.cve.org/CVERecord?id=CVE-2026-28388");
  script_set_attribute(attribute:"see_also", value:"https://www.cve.org/CVERecord?id=CVE-2026-28389");
  script_set_attribute(attribute:"see_also", value:"https://www.cve.org/CVERecord?id=CVE-2026-28390");
  script_set_attribute(attribute:"solution", value:
"Upgrade to OpenSSL version 1.1.1zg or later.");
  script_set_attribute(attribute:"agent", value:"all");
  script_set_cvss_base_vector("CVSS2#AV:N/AC:H/Au:N/C:C/I:C/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:H/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-28387");

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

  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:"stig_severity", value:"II");
  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.1zg' }
];

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