IBM MQ 9.1 < 9.1.0.34 LTS / 9.2 < 9.2.0.41 LTS / 9.3 < 9.3.0.37 LTS / 9.3 < 9.4.5.0 CD / 9.4 < 9.4.0.20 LTS (7262259)

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

include('compat.inc');

if (description)
{
  script_id(300570);
  script_version("1.1");
  script_set_attribute(attribute:"plugin_modification_date", value:"2026/03/04");

  script_cve_id(
    "CVE-2025-11187",
    "CVE-2025-15467",
    "CVE-2025-15468",
    "CVE-2025-15469",
    "CVE-2025-66199",
    "CVE-2025-68160",
    "CVE-2025-69418",
    "CVE-2025-69419",
    "CVE-2025-69420",
    "CVE-2025-69421",
    "CVE-2026-22795",
    "CVE-2026-22796"
  );

  script_name(english:"IBM MQ 9.1 < 9.1.0.34 LTS / 9.2 < 9.2.0.41 LTS / 9.3 < 9.3.0.37 LTS / 9.3 < 9.4.5.0 CD / 9.4 < 9.4.0.20 LTS (7262259)");

  script_set_attribute(attribute:"synopsis", value:
"The remote web server is affected by multiple vulnerabilities.");
  script_set_attribute(attribute:"description", value:
"The version of IBM MQ Server running on the remote host is affected by multiple vulnerabilities as referenced in the
7262259 advisory.

  - Issue summary: Processing a malformed PKCS#12 file can trigger a NULL pointer dereference in the
    PKCS12_item_decrypt_d2i_ex() function. Impact summary: A NULL pointer dereference can trigger a crash
    which leads to Denial of Service for an application processing PKCS#12 files. The
    PKCS12_item_decrypt_d2i_ex() function does not check whether the oct parameter is NULL before
    dereferencing it. When called from PKCS12_unpack_p7encdata() with a malformed PKCS#12 file, this parameter
    can be NULL, causing a crash. The vulnerability is limited to Denial of Service and cannot be escalated to
    achieve code execution or memory disclosure. Exploiting this issue requires an attacker to provide a
    malformed PKCS#12 file to an application that processes it. 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 PKCS#12 implementation is outside the OpenSSL FIPS module boundary. OpenSSL 3.6,
    3.5, 3.4, 3.3, 3.0, 1.1.1 and 1.0.2 are vulnerable to this issue. (CVE-2025-69421)

  - Issue summary: PBMAC1 parameters in PKCS#12 files are missing validation which can trigger a stack-based
    buffer overflow, invalid pointer or NULL pointer dereference during MAC verification. Impact summary: The
    stack buffer overflow or NULL pointer dereference may cause a crash leading to Denial of Service for an
    application that parses untrusted PKCS#12 files. The buffer overflow may also potentially enable code
    execution depending on platform mitigations. When verifying a PKCS#12 file that uses PBMAC1 for the MAC,
    the PBKDF2 salt and keylength parameters from the file are used without validation. If the value of
    keylength exceeds the size of the fixed stack buffer used for the derived key (64 bytes), the key
    derivation will overflow the buffer. The overflow length is attacker-controlled. Also, if the salt
    parameter is not an OCTET STRING type this can lead to invalid or NULL pointer dereference. Exploiting
    this issue requires a user or application to process a maliciously crafted PKCS#12 file. It is uncommon to
    accept untrusted PKCS#12 files in applications as they are usually used to store private keys which are
    trusted by definition. For this reason the issue was assessed as Moderate severity. The FIPS modules in
    3.6, 3.5 and 3.4 are not affected by this issue, as PKCS#12 processing is outside the OpenSSL FIPS module
    boundary. OpenSSL 3.6, 3.5 and 3.4 are vulnerable to this issue. OpenSSL 3.3, 3.0, 1.1.1 and 1.0.2 are not
    affected by this issue as they do not support PBMAC1 in PKCS#12. (CVE-2025-11187)

  - Issue summary: Parsing CMS AuthEnvelopedData or EnvelopedData message with maliciously crafted AEAD
    parameters can trigger a stack buffer overflow. Impact summary: A stack buffer overflow may lead to a
    crash, causing Denial of Service, or potentially remote code execution. When parsing CMS
    (Auth)EnvelopedData structures that use AEAD ciphers such as AES-GCM, the IV (Initialization Vector)
    encoded in the ASN.1 parameters is copied into a fixed-size stack buffer without verifying that its length
    fits the destination. An attacker can supply a crafted CMS message with an oversized IV, causing a stack-
    based out-of-bounds write before any authentication or tag verification occurs. Applications and services
    that parse untrusted CMS or PKCS#7 content using AEAD ciphers (e.g., S/MIME (Auth)EnvelopedData with AES-
    GCM) are vulnerable. Because the overflow occurs prior to authentication, no valid key material is
    required to trigger it. While exploitability to remote code execution depends on platform and toolchain
    mitigations, the stack-based write primitive represents a severe risk. The FIPS modules in 3.6, 3.5, 3.4,
    3.3 and 3.0 are not affected by this issue, as the CMS implementation is outside the OpenSSL FIPS module
    boundary. OpenSSL 3.6, 3.5, 3.4, 3.3 and 3.0 are vulnerable to this issue. OpenSSL 1.1.1 and 1.0.2 are not
    affected by this issue. (CVE-2025-15467)

  - Issue summary: If an application using the SSL_CIPHER_find() function in a QUIC protocol client or server
    receives an unknown cipher suite from the peer, a NULL dereference occurs. Impact summary: A NULL pointer
    dereference leads to abnormal termination of the running process causing Denial of Service. Some
    applications call SSL_CIPHER_find() from the client_hello_cb callback on the cipher ID received from the
    peer. If this is done with an SSL object implementing the QUIC protocol, NULL pointer dereference will
    happen if the examined cipher ID is unknown or unsupported. As it is not very common to call this function
    in applications using the QUIC protocol and the worst outcome is Denial of Service, the issue was assessed
    as Low severity. The vulnerable code was introduced in the 3.2 version with the addition of the QUIC
    protocol support. The FIPS modules in 3.6, 3.5, 3.4 and 3.3 are not affected by this issue, as the QUIC
    implementation is outside the OpenSSL FIPS module boundary. OpenSSL 3.6, 3.5, 3.4 and 3.3 are vulnerable
    to this issue. OpenSSL 3.0, 1.1.1 and 1.0.2 are not affected by this issue. (CVE-2025-15468)

  - Issue summary: The 'openssl dgst' command-line tool silently truncates input data to 16MB when using one-
    shot signing algorithms and reports success instead of an error. Impact summary: A user signing or
    verifying files larger than 16MB with one-shot algorithms (such as Ed25519, Ed448, or ML-DSA) may believe
    the entire file is authenticated while trailing data beyond 16MB remains unauthenticated. When the
    'openssl dgst' command is used with algorithms that only support one-shot signing (Ed25519, Ed448, ML-
    DSA-44, ML-DSA-65, ML-DSA-87), the input is buffered with a 16MB limit. If the input exceeds this limit,
    the tool silently truncates to the first 16MB and continues without signaling an error, contrary to what
    the documentation states. This creates an integrity gap where trailing bytes can be modified without
    detection if both signing and verification are performed using the same affected codepath. The issue
    affects only the command-line tool behavior. Verifiers that process the full message using library APIs
    will reject the signature, so the risk primarily affects workflows that both sign and verify with the
    affected 'openssl dgst' command. Streaming digest algorithms for 'openssl dgst' and library users are
    unaffected. The FIPS modules in 3.5 and 3.6 are not affected by this issue, as the command-line tools are
    outside the OpenSSL FIPS module boundary. OpenSSL 3.5 and 3.6 are vulnerable to this issue. OpenSSL 3.4,
    3.3, 3.0, 1.1.1 and 1.0.2 are not affected by this issue. (CVE-2025-15469)

  - Issue summary: A TLS 1.3 connection using certificate compression can be forced to allocate a large buffer
    before decompression without checking against the configured certificate size limit. Impact summary: An
    attacker can cause per-connection memory allocations of up to approximately 22 MiB and extra CPU work,
    potentially leading to service degradation or resource exhaustion (Denial of Service). In affected
    configurations, the peer-supplied uncompressed certificate length from a CompressedCertificate message is
    used to grow a heap buffer prior to decompression. This length is not bounded by the max_cert_list
    setting, which otherwise constrains certificate message sizes. An attacker can exploit this to cause large
    per-connection allocations followed by handshake failure. No memory corruption or information disclosure
    occurs. This issue only affects builds where TLS 1.3 certificate compression is compiled in (i.e., not
    OPENSSL_NO_COMP_ALG) and at least one compression algorithm (brotli, zlib, or zstd) is available, and
    where the compression extension is negotiated. Both clients receiving a server CompressedCertificate and
    servers in mutual TLS scenarios receiving a client CompressedCertificate are affected. Servers that do not
    request client certificates are not vulnerable to client-initiated attacks. Users can mitigate this issue
    by setting SSL_OP_NO_RX_CERTIFICATE_COMPRESSION to disable receiving compressed certificates. The FIPS
    modules in 3.6, 3.5, 3.4 and 3.3 are not affected by this issue, as the TLS implementation is outside the
    OpenSSL FIPS module boundary. OpenSSL 3.6, 3.5, 3.4 and 3.3 are vulnerable to this issue. OpenSSL 3.0,
    1.1.1 and 1.0.2 are not affected by this issue. (CVE-2025-66199)

  - Issue summary: Writing large, newline-free data into a BIO chain using the line-buffering filter where the
    next BIO performs short writes can trigger a heap-based out-of-bounds write. Impact summary: This out-of-
    bounds write can cause memory corruption which typically results in a crash, leading to Denial of Service
    for an application. The line-buffering BIO filter (BIO_f_linebuffer) is not used by default in TLS/SSL
    data paths. In OpenSSL command-line applications, it is typically only pushed onto stdout/stderr on VMS
    systems. Third-party applications that explicitly use this filter with a BIO chain that can short-write
    and that write large, newline-free data influenced by an attacker would be affected. However, the
    circumstances where this could happen are unlikely to be under attacker control, and BIO_f_linebuffer is
    unlikely to be handling non-curated data controlled by an attacker. For that reason the issue was assessed
    as Low severity. The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the BIO
    implementation is outside the OpenSSL FIPS module boundary. OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0, 1.1.1 and
    1.0.2 are vulnerable to this issue. (CVE-2025-68160)

  - Issue summary: When using the low-level OCB API directly with AES-NI or<br>other hardware-accelerated code
    paths, inputs whose length is not a multiple<br>of 16 bytes can leave the final partial block unencrypted
    and unauthenticated.<br><br>Impact summary: The trailing 1-15 bytes of a message may be exposed
    in<br>cleartext on encryption and are not covered by the authentication tag,<br>allowing an attacker to
    read or tamper with those bytes without detection.<br><br>The low-level OCB encrypt and decrypt routines
    in the hardware-accelerated<br>stream path process full 16-byte blocks but do not advance the
    input/output<br>pointers. The subsequent tail-handling code then operates on the original<br>base
    pointers, effectively reprocessing the beginning of the buffer while<br>leaving the actual trailing bytes
    unprocessed. The authentication checksum<br>also excludes the true tail bytes.<br><br>However, typical
    OpenSSL consumers using EVP are not affected because the<br>higher-level EVP and provider OCB
    implementations split inputs so that full<br>blocks and trailing partial blocks are processed in separate
    calls, avoiding<br>the problematic code path. Additionally, TLS does not use OCB ciphersuites.<br>The
    vulnerability only affects applications that call the low-level<br>CRYPTO_ocb128_encrypt() or
    CRYPTO_ocb128_decrypt() functions directly with<br>non-block-aligned lengths in a single call on hardware-
    accelerated builds.<br>For these reasons the issue was assessed as Low severity.<br><br>The FIPS modules
    in 3.6, 3.5, 3.4, 3.3, 3.2, 3.1 and 3.0 are not affected<br>by this issue, as OCB mode is not a FIPS-
    approved algorithm.<br><br>OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0 and 1.1.1 are vulnerable to this
    issue.<br><br>OpenSSL 1.0.2 is not affected by this issue. (CVE-2025-69418)

  - Issue summary: Calling PKCS12_get_friendlyname() function on a maliciously crafted PKCS#12 file with a
    BMPString (UTF-16BE) friendly name containing non-ASCII BMP code point can trigger a one byte write before
    the allocated buffer. Impact summary: The out-of-bounds write can cause a memory corruption which can have
    various consequences including a Denial of Service. The OPENSSL_uni2utf8() function performs a two-pass
    conversion of a PKCS#12 BMPString (UTF-16BE) to UTF-8. In the second pass, when emitting UTF-8 bytes, the
    helper function bmp_to_utf8() incorrectly forwards the remaining UTF-16 source byte count as the
    destination buffer capacity to UTF8_putc(). For BMP code points above U+07FF, UTF-8 requires three bytes,
    but the forwarded capacity can be just two bytes. UTF8_putc() then returns -1, and this negative value is
    added to the output length without validation, causing the length to become negative. The subsequent
    trailing NUL byte is then written at a negative offset, causing write outside of heap allocated buffer.
    The vulnerability is reachable via the public PKCS12_get_friendlyname() API when parsing attacker-
    controlled PKCS#12 files. While PKCS12_parse() uses a different code path that avoids this issue,
    PKCS12_get_friendlyname() directly invokes the vulnerable function. Exploitation requires an attacker to
    provide a malicious PKCS#12 file to be parsed by the application and the attacker can just trigger a one
    zero byte write before the allocated buffer. 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 PKCS#12 implementation is outside the OpenSSL FIPS module boundary. OpenSSL 3.6, 3.5, 3.4,
    3.3, 3.0 and 1.1.1 are vulnerable to this issue. OpenSSL 1.0.2 is not affected by this issue.
    (CVE-2025-69419)

  - Issue summary: A type confusion vulnerability exists in the TimeStamp Response verification code where an
    ASN1_TYPE union member is accessed without first validating the type, causing an invalid or NULL pointer
    dereference when processing a malformed TimeStamp Response file. Impact summary: An application calling
    TS_RESP_verify_response() with a malformed TimeStamp Response can be caused to dereference an invalid or
    NULL pointer when reading, resulting in a Denial of Service. The functions ossl_ess_get_signing_cert() and
    ossl_ess_get_signing_cert_v2() access the signing cert attribute value without validating its type. When
    the type is not V_ASN1_SEQUENCE, this results in accessing invalid memory through the ASN1_TYPE union,
    causing a crash. Exploiting this vulnerability requires an attacker to provide a malformed TimeStamp
    Response to an application that verifies timestamp responses. The TimeStamp protocol (RFC 3161) is not
    widely used and the impact of the exploit is just a Denial of Service. For these reasons the issue was
    assessed as Low severity. The FIPS modules in 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the
    TimeStamp Response implementation is outside the OpenSSL FIPS module boundary. OpenSSL 3.6, 3.5, 3.4, 3.3,
    3.0 and 1.1.1 are vulnerable to this issue. OpenSSL 1.0.2 is not affected by this issue. (CVE-2025-69420)

  - Issue summary: An invalid or NULL pointer dereference can happen in an application processing a malformed
    PKCS#12 file. Impact summary: An application processing a malformed PKCS#12 file can be caused to
    dereference an invalid or NULL pointer on memory read, resulting in a Denial of Service. A type confusion
    vulnerability exists in PKCS#12 parsing code where an ASN1_TYPE union member is accessed without first
    validating the type, causing an invalid pointer read. The location is constrained to a 1-byte address
    space, meaning any attempted pointer manipulation can only target addresses between 0x00 and 0xFF. This
    range corresponds to the zero page, which is unmapped on most modern operating systems and will reliably
    result in a crash, leading only to a Denial of Service. Exploiting this issue also requires a user or
    application to process a maliciously crafted PKCS#12 file. It is uncommon to accept untrusted PKCS#12
    files in applications as they are usually used to store private keys which are trusted by definition. For
    these reasons, the issue was assessed as Low severity. The FIPS modules in 3.5, 3.4, 3.3 and 3.0 are not
    affected by this issue, as the PKCS12 implementation is outside the OpenSSL FIPS module boundary. OpenSSL
    3.6, 3.5, 3.4, 3.3, 3.0 and 1.1.1 are vulnerable to this issue. OpenSSL 1.0.2 is not affected by this
    issue. (CVE-2026-22795)

  - Issue summary: A type confusion vulnerability exists in the signature verification of signed PKCS#7 data
    where an ASN1_TYPE union member is accessed without first validating the type, causing an invalid or NULL
    pointer dereference when processing malformed PKCS#7 data. Impact summary: An application performing
    signature verification of PKCS#7 data or calling directly the PKCS7_digest_from_attributes() function can
    be caused to dereference an invalid or NULL pointer when reading, resulting in a Denial of Service. The
    function PKCS7_digest_from_attributes() accesses the message digest attribute value without validating its
    type. When the type is not V_ASN1_OCTET_STRING, this results in accessing invalid memory through the
    ASN1_TYPE union, causing a crash. Exploiting this vulnerability requires an attacker to provide a
    malformed signed PKCS#7 to an application that verifies it. The impact of the exploit is just a Denial of
    Service, the PKCS7 API is legacy and applications should be using the CMS API instead. For these reasons
    the issue was assessed as Low severity. The FIPS modules in 3.5, 3.4, 3.3 and 3.0 are not affected by this
    issue, as the PKCS#7 parsing implementation is outside the OpenSSL FIPS module boundary. OpenSSL 3.6, 3.5,
    3.4, 3.3, 3.0, 1.1.1 and 1.0.2 are vulnerable to this issue. (CVE-2026-22796)

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://www.ibm.com/support/pages/node/7262259");
  script_set_attribute(attribute:"solution", value:
"Upgrade to IBM MQ 9.1.0.34 LTS, 9.2.0.41 LTS, 9.3.0.37 LTS, 9.4.0.20 LTS, 9.4.5.0 CD 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:POC/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:P/RL:O/RC:C");
  script_set_attribute(attribute:"cvss_score_source", value:"CVE-2025-69421");

  script_set_attribute(attribute:"exploitability_ease", value:"Exploits are available");
  script_set_attribute(attribute:"exploit_available", value:"true");

  script_set_attribute(attribute:"vuln_publication_date", value:"2024/04/09");
  script_set_attribute(attribute:"patch_publication_date", value:"2026/03/02");
  script_set_attribute(attribute:"plugin_publication_date", value:"2026/03/04");

  script_set_attribute(attribute:"plugin_type", value:"local");
  script_set_attribute(attribute:"cpe", value:"cpe:/a:ibm:websphere_mq");
  script_set_attribute(attribute:"cpe", value:"cpe:/a:ibm:mq");
  script_set_attribute(attribute:"generated_plugin", value:"current");
  script_end_attributes();

  script_category(ACT_GATHER_INFO);
  script_family(english:"Misc.");

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

  script_dependencies("ibm_mq_nix_installed.nbin", "websphere_mq_installed.nasl");
  script_require_keys("installed_sw/IBM WebSphere MQ");

  exit(0);
}

include('vcf.inc');

var app = 'IBM WebSphere MQ';

var app_info = vcf::get_app_info(app:app);

if (app_info['Type'] != 'Server')
  audit(AUDIT_HOST_NOT, 'an affected product');

var constraints;
# check if CD - less than 4 version segments or non-0 3rd (M) segment
# https://www.ibm.com/support/pages/ibm-mq-faq-long-term-support-and-continuous-delivery-releases
if (app_info['version'] =~ "^9\.([0-9]+\.?){0,2}$" || app_info['version'] =~ "^9\.[0-9]\.[1-9]")
{
  constraints = [
    { 'min_version' : '9.3', 'fixed_version' : '9.4.5.0' }
  ];
}
else
{
  constraints = [
    { 'min_version' : '9.1', 'fixed_version' : '9.1.0.34' },
    { 'min_version' : '9.2', 'fixed_version' : '9.2.0.41' },
    { 'min_version' : '9.3', 'fixed_version' : '9.3.0.37' },
    { 'min_version' : '9.4', 'fixed_version' : '9.4.0.20' }
  ];
}

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