NewStart CGSL MAIN 7.02 : tongsuo Multiple Vulnerabilities (NS-SA-2026-0106)

#%NASL_MIN_LEVEL 80900
##
# (C) Tenable, Inc.
#
# The descriptive text and package checks in this plugin were
# extracted from ZTE advisory NS-SA-2026-0106. The text
# itself is copyright (C) ZTE, Inc.
##

include('compat.inc');

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

  script_cve_id(
    "CVE-2025-68160",
    "CVE-2025-69418",
    "CVE-2025-69419",
    "CVE-2025-69420",
    "CVE-2025-69421",
    "CVE-2026-7383",
    "CVE-2026-9076",
    "CVE-2026-22795",
    "CVE-2026-28387",
    "CVE-2026-28388",
    "CVE-2026-28389",
    "CVE-2026-28390",
    "CVE-2026-34180",
    "CVE-2026-42766",
    "CVE-2026-45447"
  );

  script_name(english:"NewStart CGSL MAIN 7.02 : tongsuo Multiple Vulnerabilities (NS-SA-2026-0106)");

  script_set_attribute(attribute:"synopsis", value:
"The remote NewStart CGSL host is affected by multiple vulnerabilities.");
  script_set_attribute(attribute:"description", value:
"The remote NewStart CGSL host, running version MAIN 7.02, has tongsuo packages installed that are affected by multiple
vulnerabilities:

  - 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. (CVE-2026-28387)

  - 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)

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://security.gd-linux.com/notice/NS-SA-2026-0106");
  script_set_attribute(attribute:"see_also", value:"https://security.gd-linux.com/info/CVE-2025-68160");
  script_set_attribute(attribute:"see_also", value:"https://security.gd-linux.com/info/CVE-2025-69418");
  script_set_attribute(attribute:"see_also", value:"https://security.gd-linux.com/info/CVE-2025-69419");
  script_set_attribute(attribute:"see_also", value:"https://security.gd-linux.com/info/CVE-2025-69420");
  script_set_attribute(attribute:"see_also", value:"https://security.gd-linux.com/info/CVE-2025-69421");
  script_set_attribute(attribute:"see_also", value:"https://security.gd-linux.com/info/CVE-2026-22795");
  script_set_attribute(attribute:"see_also", value:"https://security.gd-linux.com/info/CVE-2026-28387");
  script_set_attribute(attribute:"see_also", value:"https://security.gd-linux.com/info/CVE-2026-28388");
  script_set_attribute(attribute:"see_also", value:"https://security.gd-linux.com/info/CVE-2026-28389");
  script_set_attribute(attribute:"see_also", value:"https://security.gd-linux.com/info/CVE-2026-28390");
  script_set_attribute(attribute:"see_also", value:"https://security.gd-linux.com/info/CVE-2026-34180");
  script_set_attribute(attribute:"see_also", value:"https://security.gd-linux.com/info/CVE-2026-42766");
  script_set_attribute(attribute:"see_also", value:"https://security.gd-linux.com/info/CVE-2026-45447");
  script_set_attribute(attribute:"see_also", value:"https://security.gd-linux.com/info/CVE-2026-7383");
  script_set_attribute(attribute:"see_also", value:"https://security.gd-linux.com/info/CVE-2026-9076");
  script_set_attribute(attribute:"solution", value:
"Upgrade the vulnerable CGSL tongsuo packages. Note that updated packages may not be available yet. Please contact ZTE
for more information.");
  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:POC/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:P/RL:O/RC:C");
  script_set_attribute(attribute:"cvss_score_source", value:"CVE-2026-28387");

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

  script_set_attribute(attribute:"plugin_type", value:"local");
  script_set_attribute(attribute:"cpe", value:"p-cpe:/a:zte:cgsl_main:tongsuo");
  script_set_attribute(attribute:"cpe", value:"p-cpe:/a:zte:cgsl_main:tongsuo-core");
  script_set_attribute(attribute:"cpe", value:"cpe:/o:zte:cgsl_main:7");
  script_set_attribute(attribute:"generated_plugin", value:"current");
  script_end_attributes();

  script_category(ACT_GATHER_INFO);
  script_family(english:"NewStart CGSL Local Security Checks");

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

  script_dependencies("ssh_get_info2.nasl");
  script_require_keys("Host/local_checks_enabled", "Host/ZTE-CGSL/release", "Host/ZTE-CGSL/rpm-list", "Host/cpu");

  exit(0);
}

include('rpm2.inc');

if (!get_kb_item('Host/local_checks_enabled')) audit(AUDIT_LOCAL_CHECKS_NOT_ENABLED);

var os_release = get_kb_item('Host/ZTE-CGSL/release');
if (isnull(os_release) || os_release !~ "^CGSL (MAIN|CORE)") audit(AUDIT_OS_NOT, 'NewStart Carrier Grade Server Linux');

if (os_release !~ "CGSL\sMAIN\s7\.02")
  audit(AUDIT_OS_NOT, 'NewStart CGSL MAIN 7.02');

if (!get_kb_item('Host/ZTE-CGSL/rpm-list')) audit(AUDIT_PACKAGE_LIST_MISSING);

var cpu = get_kb_item('Host/cpu');
if (isnull(cpu)) audit(AUDIT_UNKNOWN_ARCH);
if ('x86_64' >!< cpu && cpu !~ "^i[3-6]86$") audit(AUDIT_LOCAL_CHECKS_NOT_IMPLEMENTED, 'NewStart Carrier Grade Server Linux', cpu);

var flag = 0;

var pkgs = {
  'CGSL MAIN 7.02': [
    'tongsuo-8.3.3-5.zncgsl7.65',
    'tongsuo-core-8.3.3-5.zncgsl7.65'
  ]
};
var pkg_list = pkgs[os_release];
var pkg;
foreach (pkg in pkg_list)
  if (rpm_check(reference:pkg, release:'ZTE ' + os_release, rpm_spec_vers_cmp:TRUE)) flag++;

if (flag)
{
  security_report_v4(
    port       : 0,
    severity   : SECURITY_HOLE,
    extra      : rpm_report_get()
  );
  exit(0);
}
else
{
  var tested = pkg_tests_get();
  if (tested) audit(AUDIT_PACKAGE_NOT_AFFECTED, tested);
  else audit(AUDIT_PACKAGE_NOT_INSTALLED, 'tongsuo');
}