CyberRota Analysis
AI-GeneratedwolfEngine versions prior to 1.4.1 are vulnerable due to improper nonce handling in AES-CCM cipher suites for TLS 1.2 and DTLS 1.2, leading to the reuse of the same key and nonce across multiple records. This vulnerability compromises both confidentiality and integrity, as it allows for potential decryption of records and authentication tag forgery. Organizations using wolfEngine with explicitly enabled AES-CCM cipher suites should prioritize patching to mitigate these risks.
Original NVD Description
wolfEngine before 1.4.1 sources the explicit AES-CCM nonce for TLS 1.2 and DTLS 1.2 records from the record input buffer instead of the TLS sequence number carried in the additional authenticated data. Because the record layer leaves the explicit-nonce field for the cipher to populate, the value read is constant across records, so every AES-CCM record within a connection is encrypted under an identical key and nonce pair. Reusing a CCM key and nonce weakens confidentiality (identical keystream across records, so a known record recovers the others) and integrity (authentication tag forgery). Only wolfEngine is affected; wolfProvider is not. AES-GCM under wolfEngine is tracked separately. AES-CCM cipher suites are not enabled by default and must be explicitly selected, which limits exposure. TLS 1.3 and non-TLS use of the cipher are not affected.