#%NASL_MIN_LEVEL 80900
##
# (C) Tenable, Inc.
#
# The descriptive text and package checks in this plugin were
# extracted from ZTE advisory NS-SA-2025-0049. The text
# itself is copyright (C) ZTE, Inc.
##
include('compat.inc');
if (description)
{
script_id(238006);
script_version("1.2");
script_set_attribute(attribute:"plugin_modification_date", value:"2025/08/14");
script_cve_id(
"CVE-2023-0465",
"CVE-2023-0466",
"CVE-2023-5678",
"CVE-2023-6129",
"CVE-2024-9143"
);
script_xref(name:"IAVA", value:"2023-A-0158-S");
script_xref(name:"IAVA", value:"2024-A-0121-S");
script_xref(name:"IAVA", value:"2025-A-0127-S");
script_name(english:"NewStart CGSL MAIN 7.02 : openssl Multiple Vulnerabilities (NS-SA-2025-0049)");
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 openssl packages installed that are affected by multiple
vulnerabilities:
- Use of the low-level GF(2^m) elliptic curve APIs with untrusted explicit values for the field polynomial
can lead to out-of-bounds memory reads or writes. (CVE-2024-9143)
- Issue summary: Use of the low-level GF(2^m) elliptic curve APIs with untrusted explicit values for the
field polynomial can lead to out-of-bounds memory reads or writes. Impact summary: Out of bound memory
writes can lead to an application crash or even a possibility of a remote code execution, however, in all
the protocols involving Elliptic Curve Cryptography that we're aware of, either only named curves are
supported, or, if explicit curve parameters are supported, they specify an X9.62 encoding of binary
(GF(2^m)) curves that can't represent problematic input values. Thus the likelihood of existence of a
vulnerable application is low. In particular, the X9.62 encoding is used for ECC keys in X.509
certificates, so problematic inputs cannot occur in the context of processing X.509 certificates. Any
problematic use-cases would have to be using an exotic curve encoding. The affected APIs include:
EC_GROUP_new_curve_GF2m(), EC_GROUP_new_from_params(), and various supporting BN_GF2m_*() functions.
Applications working with exotic explicit binary (GF(2^m)) curve parameters, that make it possible to
represent invalid field polynomials with a zero constant term, via the above or similar APIs, may
terminate abruptly as a result of reading or writing outside of array bounds. Remote code execution cannot
easily be ruled out. The FIPS modules in 3.3, 3.2, 3.1 and 3.0 are not affected by this issue.
(CVE-2024-9143)
- Issue summary: The POLY1305 MAC (message authentication code) implementation contains a bug that might
corrupt the internal state of applications running on PowerPC CPU based platforms if the CPU provides
vector instructions. Impact summary: If an attacker can influence whether the POLY1305 MAC algorithm is
used, the application state might be corrupted with various application dependent consequences. The
POLY1305 MAC (message authentication code) implementation in OpenSSL for PowerPC CPUs restores the
contents of vector registers in a different order than they are saved. Thus the contents of some of these
vector registers are corrupted when returning to the caller. The vulnerable code is used only on newer
PowerPC processors supporting the PowerISA 2.07 instructions. The consequences of this kind of internal
application state corruption can be various - from no consequences, if the calling application does not
depend on the contents of non-volatile XMM registers at all, to the worst consequences, where the attacker
could get complete control of the application process. However unless the compiler uses the vector
registers for storing pointers, the most likely consequence, if any, would be an incorrect result of some
application dependent calculations or a crash leading to a denial of service. The POLY1305 MAC algorithm
is most frequently used as part of the CHACHA20-POLY1305 AEAD (authenticated encryption with associated
data) algorithm. The most common usage of this AEAD cipher is with TLS protocol versions 1.2 and 1.3. If
this cipher is enabled on the server a malicious client can influence whether this AEAD cipher is used.
This implies that TLS server applications using OpenSSL can be potentially impacted. However we are
currently not aware of any concrete application that would be affected by this issue therefore we consider
this a Low severity security issue. (CVE-2023-6129)
- Applications that use a non-default option when verifying certificates may be vulnerable to an attack from
a malicious CA to circumvent certain checks. Invalid certificate policies in leaf certificates are
silently ignored by OpenSSL and other certificate policy checks are skipped for that certificate. A
malicious CA could use this to deliberately assert invalid certificate policies in order to circumvent
policy checking on the certificate altogether. Policy processing is disabled by default but can be enabled
by passing the `-policy' argument to the command line utilities or by calling the
`X509_VERIFY_PARAM_set1_policies()' function. (CVE-2023-0465)
- The function X509_VERIFY_PARAM_add0_policy() is documented to implicitly enable the certificate policy
check when doing certificate verification. However the implementation of the function does not enable the
check which allows certificates with invalid or incorrect policies to pass the certificate verification.
As suddenly enabling the policy check could break existing deployments it was decided to keep the existing
behavior of the X509_VERIFY_PARAM_add0_policy() function. Instead the applications that require OpenSSL to
perform certificate policy check need to use X509_VERIFY_PARAM_set1_policies() or explicitly enable the
policy check by calling X509_VERIFY_PARAM_set_flags() with the X509_V_FLAG_POLICY_CHECK flag argument.
Certificate policy checks are disabled by default in OpenSSL and are not commonly used by applications.
(CVE-2023-0466)
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-2025-0049");
script_set_attribute(attribute:"see_also", value:"https://security.gd-linux.com/info/CVE-2023-0465");
script_set_attribute(attribute:"see_also", value:"https://security.gd-linux.com/info/CVE-2023-0466");
script_set_attribute(attribute:"see_also", value:"https://security.gd-linux.com/info/CVE-2023-5678");
script_set_attribute(attribute:"see_also", value:"https://security.gd-linux.com/info/CVE-2023-6129");
script_set_attribute(attribute:"see_also", value:"https://security.gd-linux.com/info/CVE-2024-9143");
script_set_attribute(attribute:"solution", value:
"Upgrade the vulnerable CGSL openssl 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: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:H/PR:N/UI:N/S:U/C:N/I:L/A:H");
script_set_cvss3_temporal_vector("CVSS:3.0/E:U/RL:O/RC:C");
script_set_attribute(attribute:"cvss4_vector", value:"CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N");
script_set_attribute(attribute:"cvss4_threat_vector", value:"CVSS:4.0/E:U");
script_set_attribute(attribute:"cvss_score_source", value:"CVE-2024-9143");
script_set_attribute(attribute:"cvss3_score_source", value:"CVE-2023-6129");
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:"2023/03/21");
script_set_attribute(attribute:"patch_publication_date", value:"2025/03/07");
script_set_attribute(attribute:"plugin_publication_date", value:"2025/06/09");
script_set_attribute(attribute:"plugin_type", value:"local");
script_set_attribute(attribute:"cpe", value:"p-cpe:/a:zte:cgsl_main:openssl");
script_set_attribute(attribute:"cpe", value:"p-cpe:/a:zte:cgsl_main:openssl-devel");
script_set_attribute(attribute:"cpe", value:"p-cpe:/a:zte:cgsl_main:openssl-libs");
script_set_attribute(attribute:"cpe", value:"p-cpe:/a:zte:cgsl_main:openssl-static");
script_set_attribute(attribute:"cpe", value:"cpe:/o:zte:cgsl_main:7");
script_set_attribute(attribute:"generated_plugin", value:"current");
script_set_attribute(attribute:"stig_severity", value:"I");
script_end_attributes();
script_category(ACT_GATHER_INFO);
script_family(english:"NewStart CGSL Local Security Checks");
script_copyright(english:"This script is Copyright (C) 2025 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': [
'openssl-3.0.12-3.zncgsl7.8',
'openssl-devel-3.0.12-3.zncgsl7.8',
'openssl-libs-3.0.12-3.zncgsl7.8',
'openssl-static-3.0.12-3.zncgsl7.8'
]
};
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_WARNING,
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, 'openssl');
}
Data
Build on a solid foundation with Vulners data
We provide the essential building blocks for cybersecurity solutions with comprehensive, structured, and constantly updated vulnerability and exploits data
Api
Power your application with Vulners API
The Vulners REST API offers reliable, high-performance access to vulnerability intelligence, with 99.9% SLA uptime and CDN-backed data delivery for seamless global access
App
Assess and manage vulnerabilities with Vulners tools
Built on top of Vulners' database and SDK, end-user solutions give security professionals and developers lightweight and powerful tools for vulnerability remediation