Kunpeng BoostKit 22.0.0.SPC2
OpenSSL CVE-2023-2650 Vulnerability
Trouble Ticket No. |
DTS: DTS2023053101272 Vulnerability ID: HWPSIRT-2023-33676 |
|---|---|
Symptom |
The product involves a security vulnerability in OpenSSL 1.1.1n. The external CVE number is CVE-2023-2650. An OBJECT IDENTIFIER is composed of a series of numbers - sub-identifiers - most of which have no size limit. OBJ_obj2txt() may be used to translate an ASN.1 OBJECT IDENTIFIER given in DER encoding form to its canonical numeric text form. When one of the sub-identifiers in the OBJECT IDENTIFIER is very large (10 to 100 KB, the translation to a decimal number in text may take a very long time. The time complexity is O(n^2) with 'n' being the size of the sub-identifiers in bytes (*). As a result, denial of service (DoS) may occur. |
Severity |
Minor |
Root Cause |
OpenSSL 1.1.1n used by the product has the CVE-2023-2650 vulnerability. |
Solution |
Use the OpenSSL software in which this vulnerability has been fixed. |
Impact |
None |
Test Suggestion |
Obtain the tag of OpenSSL 1.1.1n used for version build and compare it with the vulnerability fix list of the tag. If the list contains the CVE-2023-2650 vulnerability, the vulnerability has been fixed. |
Unsigned Value Assignments and Comparison
Trouble Ticket No. |
DTS: DTS2023011214964 |
|---|---|
Symptom |
According to the TscanCode scan result, the size of an unsigned variable is compared with 0, or a signed variable is assigned to an unsigned variable and then compared with 0. |
Severity |
Minor |
Solution |
The size of an unsigned variable does not need to be compared with 0. Modify the variable declaration so that the variable type is not changed during value assignment. |
Impact |
None |
Incomplete Command Parameters in the Documentation
Trouble Ticket No. |
DTS: DTS2023053002444 |
|---|---|
Symptom |
The User Guide does not include the --del –list parameter of the hal-tool service. |
Severity |
Minor |
Solution |
Add the --del –list parameter of the hal-tool service to the User Guide. |
Impact |
None |
Pointer Release and Null Check
Trouble Ticket No. |
DTS: DTS2023053002233 |
|---|---|
Symptom |
Abnormal branches are not released and null pointers are not checked. |
Severity |
Minor |
Solution |
Release the spaces or handles to which the pointers point in the abnormal branches. Check whether the parameters of the pointer type are null. |
Impact |
None |
Process Restart Failure
Trouble Ticket No. |
DTS: DTS2023020611038 |
|---|---|
Symptom |
After the permission for the haf_offload.conf configuration file on which the startup depends is set to be unwritable, the daemon process fails to be restarted using the haf-tool restart command. |
Severity |
Minor |
Root Cause |
The haf-tool restart command executes the stop command and then the start command. The stop command checks whether the daemon process is alive. If it is not alive, the stop process exits and the scheduled task of the daemon process will not be analyzed. The start command restarts the daemon process, and starts the scheduled task of the daemon process at the same time. The scheduled task executes the start command after the daemon process exits. After the first restart fails, the daemon process is not started or fails to be started, and the scheduled task of the daemon process is started. During the second restart, the following situation occasionally occurs: The stop command determines that the daemon process is not alive; therefore, the scheduled task is not stopped and it is no longer managed by the tool. As a result, when the start command is executed later, the scheduled task also executes the start command, and the two processes preempt the same port. |
Solution |
When running the stop command, stop the scheduled task first, and then checks whether any daemon process is alive. |
Impact |
None |
Test Suggestion |
|
Failure to Delete an Application Service
Trouble Ticket No. |
DTS: DTS2023030703302 |
|---|---|
Symptom |
Immediately after the haf-tool is used to stop the application executor, the application fails to be uninstalled. |
Severity |
Minor |
Root Cause |
In some cases, the file that stores the process ID is deleted repeatedly. After the second deletion fails, the process of uninstalling the application service exits directly. As a result, some key files are not deleted. |
Solution |
If an error occurs during the deletion, the system intercepts the error, displays an error message to the user, and continues to delete other related files. |
Impact |
None |
Test Suggestion |
When you run the stop or del command when pushing down or deploying an application service, either of the following messages is displayed: (1) The operation is successful. (2) The operation is successful, but some files fail to be deleted. Please check the files manually. In this case, the process exits normally, which does not affect the pushdown and deployment of the application service next time. |