Skip to main content
VulnerabilityPublished Updated

CVE-2024-23688: Tech.pegasys.discovery:discovery: Discovery uses the same AES/GCM Nonce throughout the session

Affects tech.pegasys.discovery:discoverySource GCVE Database

0
Compare
Authoritative record:CVE-2024-23688· Medium 5.3

Not known to be exploited · CVSS 5.3 Medium : upgrade to 0.4.5 when convenient.

Data as of 21 Nov 2026, 03:48 UTC

CVSS 3.1 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CISA-ADPCVSS 3.15.3
Patch
Available – fixed in 0.4.5
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Jan 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 20 Nov 2026.

What to do

Upgrade tech.pegasys.discovery:discovery to 0.4.5.

Affected software

ProductAffectedFixed in
Maventech.pegasys.discovery:discoveryAffected
  • <0.4.5
Fixed in
  • 0.4.5

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade to tech.pegasys.discovery version 0.4.5 or later, where the nonce generation per message is properly implemented to prevent session key leakage. Since a patch is available, applying this official fix is the recommended mitigation.

Description

The tech.pegasys.discovery component uses the same AES/GCM nonce throughout a session instead of generating a unique nonce per message. This improper nonce reuse can lead to the leaking of the session key used for communication with individual peers. The node's private key and the signed ENR record remain secure and cannot be altered by an attacker. A fix addressing this issue is available in version 0.4.5.

References

Community reviews

Loading reviews…