CyberRota Analysis
AI-GeneratedKong Event Gateway versions 1.0.0 through 1.1.1 and 1.2.0 are vulnerable due to inadequate enforcement of key rotation for AES-GCM encryption keys when the AWS IAM encryption feature is enabled, potentially leading to nonce collisions during high message throughput. This vulnerability allows an authorized consumer to exploit nonce collisions to recover portions of plaintext from the affected messages. Organizations using these versions should prioritize upgrading to 1.1.2 or 1.2.1 to mitigate the risk of data exposure.
Original NVD Description
Kong Event Gateway versions 1.0.0 through 1.1.1 and 1.2.0 do not enforce key rotation before reaching NIST SP 800-38D recommended usage limit for AES-GCM encryption keys with random nonces when the AWS IAM encryption feature is enabled. If a producer sends messages at a sustained high rate without key rotation, which only occurs on reboot of the Kong Event Gateway instance, the probability of a nonce collision becomes non-negligible. An authorized consumer who detects a nonce collision can recover parts of plaintext from the affected messages. New versions 1.1.2 and 1.2.1 enforce automatic key rotation before the recommended usage limit is reached.