A cryptographic flaw in wolfProvider versions before 1.2.2 allows attackers to recover encrypted data and forge authentication tags in TLS 1.2 and DTLS 1.2 connections.

The software suffers from improper nonce management (CWE-323) where the AES-GCM nonce is not incremented per record. This allows unauthenticated attackers to decrypt traffic and forge authentication tags when using TLS 1.2 or DTLS 1.2.

The inability to maintain unique nonces for AES-GCM encryption compromises the confidentiality and integrity of protected communications. With a CVSS score of 7.4, this vulnerability represents a high risk as it permits the exposure of sensitive data and the potential for session hijacking or man-in-the-middle attacks. Organizations relying on this library for secure data transmission are at risk of complete traffic decryption if an attacker can intercept the connection.

Immediate Action: Upgrade to wolfProvider version 1.2.2 or later, which correctly implements nonce incrementing.

Proactive Monitoring: Review cryptographic configurations to identify services utilizing TLS 1.2 or DTLS 1.2 and prioritize those for immediate patching.

Compensating Controls: As an interim measure, disable TLS 1.2 and DTLS 1.2 in favor of TLS 1.3, or switch the cipher suite to AES-CCM, which is not affected by this specific implementation flaw.

Public Exploit Available: Unknown

Given the critical nature of cryptographic failures, organizations should prioritize upgrading wolfProvider to version 1.2.2 immediately. If an immediate update is not feasible, migrating to TLS 1.3 or AES-CCM is a necessary step to maintain the security of communications and prevent potential data exposure or unauthorized authentication.