Lookup for vulnerable packages by Package URL.
| Purl | pkg:pypi/indy-node@1.8.0.dev956 |
|---|
| Type | pypi |
|---|
| Namespace | |
|---|
| Name | indy-node |
|---|
| Version | 1.8.0.dev956 |
|---|
| Qualifiers |
|
|---|
| Subpath | |
|---|
| Is_vulnerable | true |
|---|
| Next_non_vulnerable_version | 1.13.0.dev2 |
|---|
| Latest_non_vulnerable_version | 1.13.0.dev2 |
|---|
| Affected_by_vulnerabilities |
| 0 |
| url |
VCID-1wmm-pzr6-bba8 |
| vulnerability_id |
VCID-1wmm-pzr6-bba8 |
| summary |
Indy Node is the server portion of a distributed ledger purpose-built for decentralized identity. In versions 1.12.4 and prior, the `pool-upgrade` request handler in Indy-Node allows an improperly authenticated attacker to remotely execute code on nodes within the network. The `pool-upgrade` request handler in Indy-Node 1.12.5 has been updated to properly authenticate pool-upgrade transactions before any processing is performed by the request handler. The transactions are further sanitized to prevent remote code execution. As a workaround, endorsers should not create DIDs for untrusted users. A vulnerable ledger should configure `auth_rules` to prevent new DIDs from being written to the ledger until the network can be upgraded. |
| references |
|
| fixed_packages |
|
| aliases |
CVE-2022-31020, GHSA-r6v9-p59m-gj2p, PYSEC-2022-265
|
| risk_score |
null |
| exploitability |
null |
| weighted_severity |
null |
| resource_url |
http://public2.vulnerablecode.io/vulnerabilities/VCID-1wmm-pzr6-bba8 |
|
| 1 |
| url |
VCID-mra4-e5xt-87c5 |
| vulnerability_id |
VCID-mra4-e5xt-87c5 |
| summary |
Hyperledger Indy Node is the server portion of a distributed ledger purpose-built for decentralized identity. In Hyperledger Indy before version 1.12.4, there is lack of signature verification on a specific transaction which enables an attacker to make certain unauthorized alterations to the ledger. Updating a DID with a nym transaction will be written to the ledger if neither ROLE or VERKEY are being changed, regardless of sender. A malicious DID with no particular role can ask an update for another DID (but cannot modify its verkey or role). This is bad because 1) Any DID can write a nym transaction to the ledger (i.e., any DID can spam the ledger with nym transactions), 2) Any DID can change any other DID's alias, 3) The update transaction modifies the ledger metadata associated with a DID. |
| references |
|
| fixed_packages |
|
| aliases |
CVE-2020-11093, GHSA-wh2w-39f4-rpv2, PYSEC-2020-48
|
| risk_score |
null |
| exploitability |
null |
| weighted_severity |
null |
| resource_url |
http://public2.vulnerablecode.io/vulnerabilities/VCID-mra4-e5xt-87c5 |
|
| 2 |
| url |
VCID-pd2r-u3ft-x3cc |
| vulnerability_id |
VCID-pd2r-u3ft-x3cc |
| summary |
In Indy Node 1.12.2, there is an Uncontrolled Resource Consumption vulnerability. Indy Node has a bug in TAA handling code. The current primary can be crashed with a malformed transaction from a client, which leads to a view change. Repeated rapid view changes have the potential of bringing down the network. This is fixed in version 1.12.3. |
| references |
|
| fixed_packages |
|
| aliases |
CVE-2020-11090, GHSA-3gw4-m5w7-v89c, PYSEC-2020-47
|
| risk_score |
null |
| exploitability |
null |
| weighted_severity |
null |
| resource_url |
http://public2.vulnerablecode.io/vulnerabilities/VCID-pd2r-u3ft-x3cc |
|
| 3 |
| url |
VCID-syrt-grka-jbcx |
| vulnerability_id |
VCID-syrt-grka-jbcx |
| summary |
indy-node is the server portion of Hyperledger Indy, a distributed ledger purpose-built for decentralized identity. In vulnerable versions of indy-node, an attacker can max out the number of client connections allowed by the ledger, leaving the ledger unable to be used for its intended purpose. However, the ledger content will not be impacted and the ledger will resume functioning after the attack. This attack exploits the trade-off between resilience and availability. Any protection against abusive client connections will also prevent the network being accessed by certain legitimate users. As a result, validator nodes must tune their firewall rules to ensure the right trade-off for their network's expected users. The guidance to network operators for the use of firewall rules in the deployment of Indy networks has been modified to better protect against denial of service attacks by increasing the cost and complexity in mounting such attacks. The mitigation for this vulnerability is not in the Hyperledger Indy code per se, but rather in the individual deployments of Indy. The mitigations should be applied to all deployments of Indy, and are not related to a particular release. |
| references |
|
| fixed_packages |
|
| aliases |
CVE-2022-31006, GHSA-x996-7qh9-7ff7, PYSEC-2022-270
|
| risk_score |
null |
| exploitability |
null |
| weighted_severity |
null |
| resource_url |
http://public2.vulnerablecode.io/vulnerabilities/VCID-syrt-grka-jbcx |
|
|
|---|
| Fixing_vulnerabilities |
|
|---|
| Risk_score | null |
|---|
| Resource_url | http://public2.vulnerablecode.io/packages/pkg:pypi/indy-node@1.8.0.dev956 |
|---|