本公告载明可能影响部分谦川科技软件产品、组件或版本的安全漏洞信息。谦川科技高度重视产品及客户业务的安全。截至本公告发布之日，谦川科技尚未收到有关上述漏洞已在真实环境中被利用的报告。
| 类别 | 漏洞详情 |
| 产品名称 | Hypervisor |
| 受影响的版本 | MT8676 2os、MT8676 3os、MT8678 2os、MT8678 3os、cobranch、MT8668 2os、MT8668 3os |
| 漏洞编号 | CVE-2021-3450 |
| CVSS评分 | 7.4 |
| 漏洞标题 | CA certificate check bypass with X509_V_FLAG_X509_STRICT |
| 详细描述 | The X509_V_FLAG_X509_STRICT flag enables additional security checks of the certificates present in a certificate chain. It is not set by default. Starting from OpenSSL version 1.1.1h a check to disallow certificates in the chain that have explicitly encoded elliptic curve parameters was added as an additional strict check. An error in the implementation of this check meant that the result of a previous check to confirm that certificates in the chain are valid CA certificates was overwritten. This effectively bypasses the check that non-CA certificates must not be able to issue other certificates. If a "purpose" has been configured then there is a subsequent opportunity for checks that the certificate is a valid CA. All of the named "purpose" values implemented in libcrypto perform this check. Therefore, where a purpose is set the certificate chain will still be rejected even when the strict flag has been used. A purpose is set by default in libssl client and server certificate verification routines, but it can be overridden or removed by an application. In order to be affected, an application must explicitly set the X509_V_FLAG_X509_STRICT verification flag and either not set a purpose for the certificate verification or, in the case of TLS client or server applications, override the default purpose. OpenSSL versions 1.1.1h and newer are affected by this issue. Users of these versions should upgrade to OpenSSL 1.1.1k. OpenSSL 1.0.2 is not impacted by this issue. Fixed in OpenSSL 1.1.1k (Affected 1.1.1h-1.1.1j). |
| 受影响资产 | Nebula |
| 漏洞类型 | cve |
| 风险等级 | 高危 |
| 修复状态 | 已修复 |
| 类别 | 漏洞详情 |
| 产品名称 | Hypervisor |
| 受影响的版本 | MT8676 2os、MT8676 3os、MT8678 2os、MT8678 3os、cobranch、MT8668 2os、MT8668 3os |
| 漏洞编号 | CVE-2021-3450 |
| CVSS评分 | 7.4 |
| 漏洞标题 | CA certificate check bypass with X509_V_FLAG_X509_STRICT |
| 详细描述 | The X509_V_FLAG_X509_STRICT flag enables additional security checks of the certificates present in a certificate chain. It is not set by default. Starting from OpenSSL version 1.1.1h a check to disallow certificates in the chain that have explicitly encoded elliptic curve parameters was added as an additional strict check. An error in the implementation of this check meant that the result of a previous check to confirm that certificates in the chain are valid CA certificates was overwritten. This effectively bypasses the check that non-CA certificates must not be able to issue other certificates. If a "purpose" has been configured then there is a subsequent opportunity for checks that the certificate is a valid CA. All of the named "purpose" values implemented in libcrypto perform this check. Therefore, where a purpose is set the certificate chain will still be rejected even when the strict flag has been used. A purpose is set by default in libssl client and server certificate verification routines, but it can be overridden or removed by an application. In order to be affected, an application must explicitly set the X509_V_FLAG_X509_STRICT verification flag and either not set a purpose for the certificate verification or, in the case of TLS client or server applications, override the default purpose. OpenSSL versions 1.1.1h and newer are affected by this issue. Users of these versions should upgrade to OpenSSL 1.1.1k. OpenSSL 1.0.2 is not impacted by this issue. Fixed in OpenSSL 1.1.1k (Affected 1.1.1h-1.1.1j). |
| 受影响资产 | Nebula |
| 漏洞类型 | cve |
| 风险等级 | 高危 |
| 修复状态 | 已修复 |
| 类别 | 漏洞详情 |
| 产品名称 | Hypervisor |
| 受影响的版本 | MT8676 2os、MT8676 3os、MT8678 2os、MT8678 3os、cobranch、MT8668 2os、MT8668 3os |
| 漏洞编号 | CVE-2021-4160 |
| CVSS评分 | 5.9 |
| 漏洞标题 | BN_mod_exp may produce incorrect results on MIPS |
| 详细描述 | There is a carry propagation bug in the MIPS32 and MIPS64 squaring procedure. Many EC algorithms are affected, including some of the TLS 1.3 default curves. Impact was not analyzed in detail, because the pre-requisites for attack are considered unlikely and include reusing private keys. Analysis suggests that attacks against RSA and DSA as a result of this defect would be very difficult to perform and are not believed likely. Attacks against DH are considered just feasible (although very difficult) because most of the work necessary to deduce information about a private key may be performed offline. The amount of resources required for such an attack would be significant. However, for an attack on TLS to be meaningful, the server would have to share the DH private key among multiple clients, which is no longer an option since CVE-2016-0701. This issue affects OpenSSL versions 1.0.2, 1.1.1 and 3.0.0. It was addressed in the releases of 1.1.1m and 3.0.1 on the 15th of December 2021. For the 1.0.2 release it is addressed in git commit 6fc1aaaf3 that is available to premium support customers only. It will be made available in 1.0.2zc when it is released. The issue only affects OpenSSL on MIPS platforms. Fixed in OpenSSL 3.0.1 (Affected 3.0.0). Fixed in OpenSSL 1.1.1m (Affected 1.1.1-1.1.1l). Fixed in OpenSSL 1.0.2zc-dev (Affected 1.0.2-1.0.2zb). |
| 受影响资产 | Nebula |
| 漏洞类型 | cve |
| 风险等级 | 中危 |
| 修复状态 | 已修复 |
| 类别 | 漏洞详情 |
| 产品名称 | Hypervisor |
| 受影响的版本 | MT8676 2os、MT8676 3os、MT8678 2os、MT8678 3os、cobranch、MT8668 2os、MT8668 3os |
| 漏洞编号 | CVE-2022-0778 |
| CVSS评分 | 7.5 |
| 漏洞标题 | Infinite loop in BN_mod_sqrt() reachable when parsing certificates |
| 详细描述 | The BN_mod_sqrt() function, which computes a modular square root, contains a bug that can cause it to loop forever for non-prime moduli. Internally this function is used when parsing certificates that contain elliptic curve public keys in compressed form or explicit elliptic curve parameters with a base point encoded in compressed form. It is possible to trigger the infinite loop by crafting a certificate that has invalid explicit curve parameters. Since certificate parsing happens prior to verification of the certificate signature, any process that parses an externally supplied certificate may thus be subject to a denial of service attack. The infinite loop can also be reached when parsing crafted private keys as they can contain explicit elliptic curve parameters. Thus vulnerable situations include: - TLS clients consuming server certificates - TLS servers consuming client certificates - Hosting providers taking certificates or private keys from customers - Certificate authorities parsing certification requests from subscribers - Anything else which parses ASN.1 elliptic curve parameters Also any other applications that use the BN_mod_sqrt() where the attacker can control the parameter values are vulnerable to this DoS issue. In the OpenSSL 1.0.2 version the public key is not parsed during initial parsing of the certificate which makes it slightly harder to trigger the infinite loop. However any operation which requires the public key from the certificate will trigger the infinite loop. In particular the attacker can use a self-signed certificate to trigger the loop during verification of the certificate signature. This issue affects OpenSSL versions 1.0.2, 1.1.1 and 3.0. It was addressed in the releases of 1.1.1n and 3.0.2 on the 15th March 2022. Fixed in OpenSSL 3.0.2 (Affected 3.0.0,3.0.1). Fixed in OpenSSL 1.1.1n (Affected 1.1.1-1.1.1m). Fixed in OpenSSL 1.0.2zd (Affected 1.0.2-1.0.2zc). |
| 受影响资产 | Nebula |
| 漏洞类型 | cve |
| 风险等级 | 高危 |
| 修复状态 | 已修复 |
