github.com/hyperledger/fabric v2.1.1+incompatible
PkgFire would install this release with a warning.·Checked 8 hours ago·Published 1 June 2020
Why
-
warnVulnerability
Hyperledger Fabric does not verify request has a timestamp within the expected time window in github.com/hyperledger/fabric
-
warnVulnerability
Hyperledger Fabric does not verify request has a timestamp within the expected time window
-
warnVulnerability
Hyperledger Fabric vulnerable to Improper Input Validation in orderer/common/cluster consensus request (fixed in 2.2.7)
-
warnVulnerability
Hyperledger Fabric subject to Denial of Service via non-validated request (fixed in 2.4.6)
-
warnVulnerability
HTTP Request Smuggling in github.com/hyperledger/fabric (fixed in 2.4.0)
-
warnVulnerability
Fabric vulnerable to crosslinking transaction attack (fixed in 2.2.14)
-
warnVulnerability
NULL Pointer Dereference in HyperLedger Fabric (fixed in 2.2.4)
What the code does
On its own this is weak signal: plenty of honest libraries read files or talk to the network. What PkgFire watches is a release gaining something the one before it did not.
Source patterns
Patterns found in the source, including those malware is known to use.
Check every dependency before it installs
This page is one release. PkgFire checks every package in your lockfile, on every install and in every pull request, and blocks the bad ones before they run.