openHiTLS Security Advisory: Side-channel, Memory Leak, RNG Reuse, and Validation Vulnerabilities

Vulnerability Overview Several security-related vulnerabilities have been identified in the openHiTLS project, primarily including: 1. Data Validation Issues: Data validation issues exist within the MIDSA algorithm. 2. Length Calculation Errors: Length calculation errors may occur during SM2 decoding. 3. Side-Channel Vulnerabilities: Side-channel vulnerabilities exist in the rejection sampling process of MLDSA. 4. Memory Leaks: Memory leak issues exist during . 5. Unreported Errors: In SM4-OCM mode, errors are not reported when the key carries specific values. 6. Insecure Memory Clearing: Insecure memory clearing functions are in use. 7. Random Number Reuse: In , the non-deterministic mode reuses the same random number. 8. Insufficient Input Validation: Insufficient input validation exists in DRBG and entropy sources. 9. Timing-Constant Decoders: Timing-constant decoder issues exist in McEliece. 10. Sensitive Data Erasure: Issues with sensitive data erasure exist. 11. Hash Algorithm Security Bit Checks: Issues with hash algorithm security bit checks exist within X.509 certificate chains. 12. Hash Erasure and Contraction: Issues with hash erasure and contraction exist. 13. Custom Extension Rejection: Issues exist regarding the rejection of registered custom extensions. 14. Compilation Warnings: Issues exist with clearing code compilation warnings. 15. Flag Information Copying and Deletion: Issues exist with copying and deleting flag information. 16. Sensitive Information Clearing: Issues exist with clearing sensitive information. Impact Scope These vulnerabilities may affect applications using the openHiTLS library, particularly in the following aspects: Data Integrity: Data validation issues may lead to data corruption or erroneous processing. Security: Vulnerabilities such as side-channel attacks, memory leaks, unreported errors, insecure memory clearing, random number reuse, insufficient input validation, timing-constant decoders, sensitive data erasure, hash algorithm security bit checks, hash erasure and contraction, and custom extension rejection may lead to security breaches, such as data leakage and identity forgery. Stability: Length calculation errors and memory leaks may cause application crashes or instability. Remediation 1. Data Validation: Fix data validation issues in the MIDSA algorithm to ensure data correctness. 2. Length Calculation: Correct length calculation errors during SM2 decoding. 3. Side-Channel Protection: Enhance side-channel protection for MLDSA rejection sampling. 4. Memory Management: Fix memory leaks in . 5. Error Reporting: Ensure proper error reporting in SM4-OCM mode. 6. Secure Memory Clearing: Use secure memory clearing functions. 7. Random Number Generation: Avoid reusing the same random number in . 8. Input Validation: Strengthen input validation for DRBG and entropy sources. 9. Timing-Constant Decoding: Fix timing-constant decoder issues in McEliece. 10. Sensitive Data Erasure: Ensure sensitive data is properly erased. 11. Hash Algorithm Checks: Add security bit checks for hash algorithms in X.509 certificate chains. 12. Hash Operations: Fix issues related to hash erasure and contraction. 13. Custom Extensions: Properly handle the registration and rejection of custom extensions. 14. Compilation Warnings: Clean up compilation warnings in the code. 15. Flag Information: Properly handle the copying and deletion of flag information. 16. Sensitive Information Clearing: Ensure sensitive information is properly cleared. POC Code or Exploit Code No specific POC code or exploit code is provided on the page.

Goal Reached Thanks to every supporter — we hit 100%!

openHiTLS Security Advisory: Side-channel, Memory Leak, RNG Reuse, and Validation Vulnerabilities

More from this source