本公告载明可能影响部分谦川科技软件产品、组件或版本的安全漏洞信息。谦川科技高度重视产品及客户业务的安全。截至本公告发布之日，谦川科技尚未收到有关上述漏洞已在真实环境中被利用的报告。
| 类别 | 漏洞详情 |
| 产品名称 | Hypervisor |
| 受影响的版本 | MT8676 2os、MT8676 3os、MT8678 2os、MT8678 3os、cobranch、MT8668 2os、MT8668 3os |
| 漏洞编号 | CVE-2024-45337 |
| CVSS评分 | 9.1 |
| 漏洞标题 | Misuse of connection.serverAuthenticate may cause authorization bypass in golang.org/x/crypto |
| 详细描述 | Applications and libraries which misuse the ServerConfig.PublicKeyCallback callback may be susceptible to an authorization bypass. The documentation for ServerConfig.PublicKeyCallback says that "A call to this function does not guarantee that the key offered is in fact used to authenticate." Specifically, the SSH protocol allows clients to inquire about whether a public key is acceptable before proving control of the corresponding private key. PublicKeyCallback may be called with multiple keys, and the order in which the keys were provided cannot be used to infer which key the client successfully authenticated with, if any. Some applications, which store the key(s) passed to PublicKeyCallback (or derived information) and make security relevant determinations based on it once the connection is established, may make incorrect assumptions. For example, an attacker may send public keys A and B, and then authenticate with A. PublicKeyCallback would be called only twice, first with A and then with B. A vulnerable application may then make authorization decisions based on key B for which the attacker does not actually control the private key. Since this API is widely misused, as a partial mitigation golang.org/x/crypto@v0.31.0 enforces the property that, when successfully authenticating via public key, the last key passed to ServerConfig.PublicKeyCallback will be the key used to authenticate the connection. PublicKeyCallback will now be called multiple times with the same key, if necessary. Note that the client may still not control the last key passed to PublicKeyCallback if the connection is then authenticated with a different method, such as PasswordCallback, KeyboardInteractiveCallback, or NoClientAuth. Users should be using the Extensions field of the Permissions return value from the various authentication callbacks to record data associated with the authentication attempt instead of referencing external state. Once the connection is established the state corresponding to the successful authentication attempt can be retrieved via the ServerConn.Permissions field. Note that some third-party libraries misuse the Permissions type by sharing it across authentication attempts; users of third-party libraries should refer to the relevant projects for guidance. |
| 受影响资产 | Nebula |
| 漏洞类型 | cve |
| 风险等级 | 超危 |
| 修复状态 | 已修复 |
| 类别 | 漏洞详情 |
| 产品名称 | Hypervisor |
| 受影响的版本 | MT8676 2os、MT8676 3os、MT8678 2os、MT8678 3os、cobranch、MT8668 2os、MT8668 3os |
| 漏洞编号 | CVE-2024-45338 |
| CVSS评分 | 9.1 |
| 漏洞标题 | Non-linear parsing of case-insensitive content in golang.org/x/net/html |
| 详细描述 | An attacker can craft an input to the Parse functions that would be processed non-linearly with respect to its length, resulting in extremely slow parsing. This could cause a denial of service. |
| 受影响资产 | Nebula |
| 漏洞类型 | cve |
| 风险等级 | 超危 |
| 修复状态 | 已修复 |
| 类别 | 漏洞详情 |
| 产品名称 | Hypervisor |
| 受影响的版本 | MT8676 2os、MT8676 3os、MT8678 2os、MT8678 3os、cobranch、MT8668 2os、MT8668 3os |
| 漏洞编号 | CVE-2024-39684 |
| CVSS评分 | 5.9 |
| 漏洞标题 | Tencent RapidJSON include/rapidjson/reader.h GenericReader::ParseNumber() Function Template Exponent Parsing Integer Overflow |
| 详细描述 | Tencent RapidJSON is vulnerable to privilege escalation due to an integer overflow in the GenericReader::ParseNumber() function of include/rapidjson/reader.h when parsing JSON text from a stream. An attacker needs to send the victim a crafted file which needs to be opened; this triggers the integer overflow vulnerability (when the file is parsed), leading to elevation of privilege. |
| 受影响资产 | Nebula |
| 漏洞类型 | cve |
| 风险等级 | 中危 |
| 修复状态 | 已修复 |
| 类别 | 漏洞详情 |
| 产品名称 | Hypervisor |
| 受影响的版本 | MT8676 2os、MT8676 3os、MT8678 2os、MT8678 3os、cobranch、MT8668 2os、MT8668 3os |
| 漏洞编号 | CVE-2024-38517 |
| CVSS评分 | 5.9 |
| 漏洞标题 | Tencent RapidJSON include/rapidjson/reader.h GenericReader::ParseNumber() Function Template Exponent Parsing Integer Underflow |
| 详细描述 | Tencent RapidJSON is vulnerable to privilege escalation due to an integer underflow in the `GenericReader::ParseNumber()` function of `include/rapidjson/reader.h` when parsing JSON text from a stream. An attacker needs to send the victim a crafted file which needs to be opened; this triggers the integer underflow vulnerability (when the file is parsed), leading to elevation of privilege. |
| 受影响资产 | Nebula |
| 漏洞类型 | cve |
| 风险等级 | 中危 |
| 修复状态 | 已修复 |
| 类别 | 漏洞详情 |
| 产品名称 | Hypervisor |
| 受影响的版本 | MT8676 2os、MT8676 3os、MT8678 2os、MT8678 3os、cobranch、MT8668 2os、MT8668 3os |
| 漏洞编号 | CVE-2020-1971 |
| CVSS评分 | 7.5 |
| 漏洞标题 | EDIPARTYNAME NULL pointer dereference |
| 详细描述 | The X.509 GeneralName type is a generic type for representing different types of names. One of those name types is known as EDIPartyName. OpenSSL provides a function GENERAL_NAME_cmp which compares different instances of a GENERAL_NAME to see if they are equal or not. This function behaves incorrectly when both GENERAL_NAMEs contain an EDIPARTYNAME. A NULL pointer dereference and a crash may occur leading to a possible denial of service attack. OpenSSL itself uses the GENERAL_NAME_cmp function for two purposes: 1) Comparing CRL distribution point names between an available CRL and a CRL distribution point embedded in an X509 certificate 2) When verifying that a timestamp response token signer matches the timestamp authority name (exposed via the API functions TS_RESP_verify_response and TS_RESP_verify_token) If an attacker can control both items being compared then that attacker could trigger a crash. For example if the attacker can trick a client or server into checking a malicious certificate against a malicious CRL then this may occur. Note that some applications automatically download CRLs based on a URL embedded in a certificate. This checking happens prior to the signatures on the certificate and CRL being verified. OpenSSL's s_server, s_client and verify tools have support for the "-crl_download" option which implements automatic CRL downloading and this attack has been demonstrated to work against those tools. Note that an unrelated bug means that affected versions of OpenSSL cannot parse or construct correct encodings of EDIPARTYNAME. However it is possible to construct a malformed EDIPARTYNAME that OpenSSL's parser will accept and hence trigger this attack. All OpenSSL 1.1.1 and 1.0.2 versions are affected by this issue. Other OpenSSL releases are out of support and have not been checked. Fixed in OpenSSL 1.1.1i (Affected 1.1.1-1.1.1h). Fixed in OpenSSL 1.0.2x (Affected 1.0.2-1.0.2w). |
| 受影响资产 | Nebula |
| 漏洞类型 | cve |
| 风险等级 | 高危 |
| 修复状态 | 已修复 |
| 类别 | 漏洞详情 |
| 产品名称 | Hypervisor |
| 受影响的版本 | MT8676 2os、MT8676 3os、MT8678 2os、MT8678 3os、cobranch、MT8668 2os、MT8668 3os |
| 漏洞编号 | CVE-2021-23841 |
| CVSS评分 | 7.5 |
| 漏洞标题 | Null pointer deref in X509_issuer_and_serial_hash() |
| 详细描述 | The OpenSSL public API function X509_issuer_and_serial_hash() attempts to create a unique hash value based on the issuer and serial number data contained within an X509 certificate. However it fails to correctly handle any errors that may occur while parsing the issuer field (which might occur if the issuer field is maliciously constructed). This may subsequently result in a NULL pointer deref and a crash leading to a potential denial of service attack. The function X509_issuer_and_serial_hash() is never directly called by OpenSSL itself so applications are only vulnerable if they use this function directly and they use it on certificates that may have been obtained from untrusted sources. OpenSSL versions 1.1.1i and below are affected by this issue. Users of these versions should upgrade to OpenSSL 1.1.1j. OpenSSL versions 1.0.2x and below are affected by this issue. However OpenSSL 1.0.2 is out of support and no longer receiving public updates. Premium support customers of OpenSSL 1.0.2 should upgrade to 1.0.2y. Other users should upgrade to 1.1.1j. Fixed in OpenSSL 1.1.1j (Affected 1.1.1-1.1.1i). Fixed in OpenSSL 1.0.2y (Affected 1.0.2-1.0.2x). |
| 受影响资产 | Nebula |
| 漏洞类型 | cve |
| 风险等级 | 高危 |
| 修复状态 | 已修复 |
| 类别 | 漏洞详情 |
| 产品名称 | Hypervisor |
| 受影响的版本 | MT8676 2os、MT8676 3os、MT8678 2os、MT8678 3os、cobranch、MT8668 2os、MT8668 3os |
| 漏洞编号 | CVE-2021-3712 |
| CVSS评分 | 7.4 |
| 漏洞标题 | Read buffer overruns processing ASN.1 strings |
| 详细描述 | ASN.1 strings are represented internally within OpenSSL as an ASN1_STRING structure which contains a buffer holding the string data and a field holding the buffer length. This contrasts with normal C strings which are repesented as a buffer for the string data which is terminated with a NUL (0) byte. Although not a strict requirement, ASN.1 strings that are parsed using OpenSSL's own "d2i" functions (and other similar parsing functions) as well as any string whose value has been set with the ASN1_STRING_set() function will additionally NUL terminate the byte array in the ASN1_STRING structure. However, it is possible for applications to directly construct valid ASN1_STRING structures which do not NUL terminate the byte array by directly setting the "data" and "length" fields in the ASN1_STRING array. This can also happen by using the ASN1_STRING_set0() function. Numerous OpenSSL functions that print ASN.1 data have been found to assume that the ASN1_STRING byte array will be NUL terminated, even though this is not guaranteed for strings that have been directly constructed. Where an application requests an ASN.1 structure to be printed, and where that ASN.1 structure contains ASN1_STRINGs that have been directly constructed by the application without NUL terminating the "data" field, then a read buffer overrun can occur. The same thing can also occur during name constraints processing of certificates (for example if a certificate has been directly constructed by the application instead of loading it via the OpenSSL parsing functions, and the certificate contains non NUL terminated ASN1_STRING structures). It can also occur in the X509_get1_email(), X509_REQ_get1_email() and X509_get1_ocsp() functions. If a malicious actor can cause an application to directly construct an ASN1_STRING and then process it through one of the affected OpenSSL functions then this issue could be hit. This might result in a crash (causing a Denial of Service attack). It could also result in the disclosure of private memory contents (such as private keys, or sensitive plaintext). Fixed in OpenSSL 1.1.1l (Affected 1.1.1-1.1.1k). Fixed in OpenSSL 1.0.2za (Affected 1.0.2-1.0.2y). |
| 受影响资产 | Nebula |
| 漏洞类型 | cve |
| 风险等级 | 高危 |
| 修复状态 | 已修复 |
| 类别 | 漏洞详情 |
| 产品名称 | Hypervisor |
| 受影响的版本 | MT8676 2os、MT8676 3os、MT8678 2os、MT8678 3os、cobranch、MT8668 2os、MT8668 3os |
| 漏洞编号 | CVE-2021-3711 |
| CVSS评分 | 9.8 |
| 漏洞标题 | SM2 Decryption Buffer Overflow |
| 详细描述 | In order to decrypt SM2 encrypted data an application is expected to call the API function EVP_PKEY_decrypt(). Typically an application will call this function twice. The first time, on entry, the "out" parameter can be NULL and, on exit, the "outlen" parameter is populated with the buffer size required to hold the decrypted plaintext. The application can then allocate a sufficiently sized buffer and call EVP_PKEY_decrypt() again, but this time passing a non-NULL value for the "out" parameter. A bug in the implementation of the SM2 decryption code means that the calculation of the buffer size required to hold the plaintext returned by the first call to EVP_PKEY_decrypt() can be smaller than the actual size required by the second call. This can lead to a buffer overflow when EVP_PKEY_decrypt() is called by the application a second time with a buffer that is too small. A malicious attacker who is able present SM2 content for decryption to an application could cause attacker chosen data to overflow the buffer by up to a maximum of 62 bytes altering the contents of other data held after the buffer, possibly changing application behaviour or causing the application to crash. The location of the buffer is application dependent but is typically heap allocated. Fixed in OpenSSL 1.1.1l (Affected 1.1.1-1.1.1k). |
| 受影响资产 | Nebula |
| 漏洞类型 | cve |
| 风险等级 | 超危 |
| 修复状态 | 已修复 |
| 类别 | 漏洞详情 |
| 产品名称 | Hypervisor |
| 受影响的版本 | MT8676 2os、MT8676 3os、MT8678 2os、MT8678 3os、cobranch、MT8668 2os、MT8668 3os |
| 漏洞编号 | CVE-2022-1292 |
| CVSS评分 | 9.8 |
| 漏洞标题 | The c_rehash script allows command injection |
| 详细描述 | The c_rehash script does not properly sanitise shell metacharacters to prevent command injection. This script is distributed by some operating systems in a manner where it is automatically executed. On such operating systems, an attacker could execute arbitrary commands with the privileges of the script. Use of the c_rehash script is considered obsolete and should be replaced by the OpenSSL rehash command line tool. Fixed in OpenSSL 3.0.3 (Affected 3.0.0,3.0.1,3.0.2). Fixed in OpenSSL 1.1.1o (Affected 1.1.1-1.1.1n). Fixed in OpenSSL 1.0.2ze (Affected 1.0.2-1.0.2zd). |
| 受影响资产 | Nebula |
| 漏洞类型 | cve |
| 风险等级 | 超危 |
| 修复状态 | 已修复 |
| 类别 | 漏洞详情 |
| 产品名称 | Hypervisor |
| 受影响的版本 | MT8676 2os、MT8676 3os、MT8678 2os、MT8678 3os、cobranch、MT8668 2os、MT8668 3os |
| 漏洞编号 | CVE-2022-2068 |
| CVSS评分 | 9.8 |
| 漏洞标题 | The c_rehash script allows command injection |
| 详细描述 | In addition to the c_rehash shell command injection identified in CVE-2022-1292, further circumstances where the c_rehash script does not properly sanitise shell metacharacters to prevent command injection were found by code review. When the CVE-2022-1292 was fixed it was not discovered that there are other places in the script where the file names of certificates being hashed were possibly passed to a command executed through the shell. This script is distributed by some operating systems in a manner where it is automatically executed. On such operating systems, an attacker could execute arbitrary commands with the privileges of the script. Use of the c_rehash script is considered obsolete and should be replaced by the OpenSSL rehash command line tool. Fixed in OpenSSL 3.0.4 (Affected 3.0.0,3.0.1,3.0.2,3.0.3). Fixed in OpenSSL 1.1.1p (Affected 1.1.1-1.1.1o). Fixed in OpenSSL 1.0.2zf (Affected 1.0.2-1.0.2ze). |
| 受影响资产 | Nebula |
| 漏洞类型 | cve |
| 风险等级 | 超危 |
| 修复状态 | 已修复 |
