Bug 2156732 (CVE-2021-4239)

Summary: CVE-2021-4239 noise: Improper nonce handling: potential overflow, potential state DoS
Product: [Other] Security Response Reporter: Avinash Hanwate <ahanwate>
Component: vulnerabilityAssignee: Red Hat Product Security <security-response-team>
Status: CLOSED UPSTREAM QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: unspecifiedKeywords: Security
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-12-29 08:32:15 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 2156733, 2156734    
Bug Blocks:    

Description Avinash Hanwate 2022-12-28 11:34:16 UTC 
The Noise protocol implementation suffers from weakened cryptographic security after encrypting 2^64 messages, and a potential denial of service attack. After 2^64 (~18.4 quintillion) messages are encrypted with the Encrypt function, the nonce counter will wrap around, causing multiple messages to be encrypted with the same key and nonce. In a separate issue, the Decrypt function increments the nonce state even when it fails to decrypt a message. If an attacker can provide an invalid input to the Decrypt function, this will cause the nonce state to desynchronize between the peers, resulting in a failure to encrypt all subsequent messages.

https://github.com/flynn/noise/pull/44
https://pkg.go.dev/vuln/GO-2022-0425
Comment 1 Avinash Hanwate 2022-12-28 11:34:51 UTC 
Created golang-github-flynn-noise tracking bugs for this issue:

Affects: fedora-all [bug 2156734]


Created nebula tracking bugs for this issue:

Affects: fedora-all [bug 2156733]
Comment 2 Product Security DevOps Team 2022-12-29 08:32:14 UTC 
This CVE Bugzilla entry is for community support informational purposes only as it does not affect a package in a commercially supported Red Hat product. Refer to the dependent bugs for status of those individual community products.