Skip to content
Fencer Vulns
medium 5.3

CVE-2024-45244 json

Hyperledger Fabric does not verify request has a timestamp within the expected time window

published 2024-08-25 2 y ago modified 2026-09-08 2 mo ago also BIT-hyperledger-fabric-orderer-2024-45244 , BIT-hyperledger-fabric-peer-2024-45244 , BIT-hyperledger-fabric-tools-2024-45244 , EUVD-2024-2485 , GHSA-48gg-32q2-4r6m , GO-2024-3099

cvss
5.3
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.6%
EPSS 0.6% chance of exploitation in 30 days, percentile 48%
public exploits
0
none known

Summary

Hyperledger Fabric through 3.0.0 and 2.5.x through 2.5.9 do not verify that a request has a timestamp within the expected time window.

Patch / fix

  • bitnami hyperledger-fabric-orderer 2.5.10
  • bitnami hyperledger-fabric-peer 2.5.10
  • bitnami hyperledger-fabric-tools 2.5.10

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
2 y ago

Exploit prediction

0.59% chance of exploitation in the next 30 days, higher than 48% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CISA ADP 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
GitHub 3.1 5.4 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
NVD 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
CNA 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
OSV 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Affected packages

ecosystem package affected fixed in
go github.com/hyperledger/fabric
<=2.5.9
all versions
no fix listed
bitnami hyperledger-fabric-orderer
<2.5.10
2.5.10
bitnami hyperledger-fabric-peer
<2.5.10
2.5.10
bitnami hyperledger-fabric-tools
<2.5.10
2.5.10

Affected products

  • hyperledger fabric

Classification

Weakness
  • CWE-294 Authentication Bypass by Capture-replay
  • CWE-285 Improper Authorization
  • CWE-672 Operation on a Resource after Expiration or Release

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.