Consensys Discovery versions less than 0.4.5 uses the same AES/GCM nonce for the entire session. which should ideally be unique for every message. The node's private key isn't compromised, only the session key generated for specific peer communication is exposed.
Metrics
Affected Vendors & Products
Advisories
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-w3hj-wr2q-x83g | Discovery uses the same AES/GCM Nonce throughout the session |
Fixes
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
References
History
Sat, 29 Nov 2025 02:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Consensys Discovery versions less than 0.4.5 uses the same AES/GCM nonce for the entire session. which should ideally be unique for every message. The node's private key isn't compromised, only the session key generated for specific peer communication is exposed. | Consensys Discovery versions less than 0.4.5 uses the same AES/GCM nonce for the entire session. which should ideally be unique for every message. The node's private key isn't compromised, only the session key generated for specific peer communication is exposed. |
Fri, 20 Jun 2025 19:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Status: PUBLISHED
Assigner: VulnCheck
Published:
Updated: 2025-11-29T02:02:09.730Z
Reserved: 2024-01-19T17:35:09.985Z
Link: CVE-2024-23688
Updated: 2024-08-01T23:06:25.353Z
Status : Modified
Published: 2024-01-19T22:15:08.563
Modified: 2025-11-29T03:15:57.600
Link: CVE-2024-23688
No data.
OpenCVE Enrichment
No data.
Github GHSA