CVE-2022-31006

HIGHNVD 7.57.5
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2022-09-16. NVD baseline CVSS 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 3 sources updated this week
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 7.5Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
49(Track)
EG Risk 49/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation1% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
57.8%
KEV
Not listed

Published

September 9, 2022

Last Modified

November 21, 2024

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
pipindy-nodeghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
indy-node0.0.1.dev38 ... 1.9.2rc1 (420 versions)1.13.0.dev2

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 14× in last 7d / 50× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 109 total refreshes for this CVE.

  1. 2026-07-23 02:11 UTCEG score recompute
  2. 2026-07-22 22:58 UTCEG score recompute
  3. 2026-07-22 14:06 UTCEPSS rescore
  4. 2026-07-22 14:06 UTCEPSS rescore
  5. 2026-07-21 15:22 UTCEPSS rescore
  6. 2026-07-21 15:22 UTCEPSS rescore
  7. 2026-07-20 17:05 UTCEPSS rescore
  8. 2026-07-19 14:29 UTCEPSS rescore
  9. 2026-07-19 02:27 UTCEPSS rescore
  10. 2026-07-19 02:27 UTCEPSS rescore
  11. 2026-07-18 10:03 UTCEPSS rescore
  12. 2026-07-18 10:02 UTCEPSS rescore
  13. 2026-07-16 20:34 UTCOSV refresh
  14. 2026-07-16 17:00 UTCEPSS rescore
  15. 2026-07-15 16:56 UTCEPSS rescore
  16. 2026-07-15 16:56 UTCEPSS rescore
  17. 2026-07-15 01:58 UTCEPSS rescore
  18. 2026-07-15 01:58 UTCEPSS rescore
  19. 2026-07-13 22:27 UTCEPSS rescore
  20. 2026-07-13 06:11 UTCEPSS rescore
  21. 2026-07-13 06:11 UTCEPSS rescore
  22. 2026-07-12 05:44 UTCEPSS rescore
  23. 2026-07-12 05:44 UTCEPSS rescore
  24. 2026-07-11 08:25 UTCEPSS rescore
  25. 2026-07-11 08:25 UTCEPSS rescore
Show 75 more
  1. 2026-07-09 19:07 UTCEPSS rescore
  2. 2026-07-08 15:12 UTCEPSS rescore
  3. 2026-07-07 13:44 UTCEPSS rescore
  4. 2026-07-06 16:25 UTCEPSS rescore
  5. 2026-07-06 16:25 UTCEPSS rescore
  6. 2026-07-06 02:21 UTCEPSS rescore
  7. 2026-07-06 02:21 UTCEPSS rescore
  8. 2026-07-05 02:28 UTCEPSS rescore
  9. 2026-07-05 02:28 UTCEPSS rescore
  10. 2026-07-04 06:29 UTCEPSS rescore
  11. 2026-07-04 06:29 UTCEPSS rescore
  12. 2026-07-01 15:04 UTCEPSS rescore
  13. 2026-06-30 23:20 UTCEPSS rescore
  14. 2026-06-30 23:20 UTCEPSS rescore
  15. 2026-06-29 14:04 UTCEPSS rescore
  16. 2026-06-28 19:02 UTCOSV refresh
  17. 2026-06-28 14:06 UTCEPSS rescore
  18. 2026-06-28 04:54 UTCEPSS rescore
  19. 2026-06-27 03:07 UTCEPSS rescore
  20. 2026-06-25 13:48 UTCEPSS rescore
  21. 2026-06-25 13:48 UTCEPSS rescore
  22. 2026-06-24 14:03 UTCEPSS rescore
  23. 2026-06-24 14:03 UTCEPSS rescore
  24. 2026-06-23 21:31 UTCEPSS rescore
  25. 2026-06-23 21:31 UTCEPSS rescore
  26. 2026-06-22 14:24 UTCEPSS rescore
  27. 2026-06-22 14:24 UTCEPSS rescore
  28. 2026-06-21 14:55 UTCEPSS rescore
  29. 2026-06-21 14:55 UTCEPSS rescore
  30. 2026-06-21 01:58 UTCEPSS rescore
  31. 2026-06-21 01:58 UTCEPSS rescore
  32. 2026-06-19 19:24 UTCEPSS rescore
  33. 2026-06-19 19:24 UTCEPSS rescore
  34. 2026-06-18 17:51 UTCEPSS rescore
  35. 2026-06-18 17:51 UTCEPSS rescore
  36. 2026-06-17 17:51 UTCEPSS rescore
  37. 2026-06-17 17:51 UTCEPSS rescore
  38. 2026-06-16 17:51 UTCEPSS rescore
  39. 2026-06-16 17:51 UTCEPSS rescore
  40. 2026-06-15 17:46 UTCEPSS rescore
  41. 2026-06-14 23:15 UTCEPSS rescore
  42. 2026-06-13 22:58 UTCEPSS rescore
  43. 2026-06-12 23:10 UTCEPSS rescore
  44. 2026-06-12 23:10 UTCEPSS rescore
  45. 2026-06-11 13:58 UTCEPSS rescore
  46. 2026-06-11 13:58 UTCEPSS rescore
  47. 2026-06-11 12:09 UTCOSV refresh
  48. 2026-06-10 22:16 UTCEPSS rescore
  49. 2026-06-10 13:20 UTCEPSS rescore
  50. 2026-06-08 14:15 UTCEPSS rescore
  51. 2026-06-08 14:15 UTCEPSS rescore
  52. 2026-06-07 15:23 UTCEPSS rescore
  53. 2026-06-07 15:23 UTCEPSS rescore
  54. 2026-06-07 15:23 UTCEPSS rescore
  55. 2026-06-06 13:46 UTCEPSS rescore
  56. 2026-06-06 13:46 UTCEPSS rescore
  57. 2026-06-05 22:45 UTCEPSS rescore
  58. 2026-06-05 22:45 UTCEPSS rescore
  59. 2026-06-05 06:09 UTCEPSS rescore
  60. 2026-06-05 06:09 UTCEPSS rescore
  61. 2026-06-04 13:11 UTCEPSS rescore
  62. 2026-06-04 13:11 UTCEPSS rescore
  63. 2026-06-02 20:11 UTCEPSS rescore
  64. 2026-06-02 20:11 UTCEPSS rescore
  65. 2026-06-02 20:11 UTCEPSS rescore
  66. 2026-05-31 22:29 UTCEPSS rescore
  67. 2026-05-31 22:29 UTCEPSS rescore
  68. 2026-05-31 22:29 UTCEPSS rescore
  69. 2026-05-31 00:15 UTCEPSS rescore
  70. 2026-05-31 00:15 UTCEPSS rescore
  71. 2026-05-29 13:43 UTCEPSS rescore
  72. 2026-05-29 13:42 UTCEPSS rescore
  73. 2026-05-28 13:43 UTCEPSS rescore
  74. 2026-05-28 13:43 UTCEPSS rescore
  75. 2026-05-28 13:43 UTCEPSS rescore

Frequently asked(5)

What is CVE-2022-31006?
CVE-2022-31006 is a high vulnerability published on September 9, 2022. 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.…
When was CVE-2022-31006 disclosed?
CVE-2022-31006 was first published in the National Vulnerability Database on September 9, 2022, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2022-31006 actively exploited?
CVE-2022-31006 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 57.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2022-31006?
CVE-2022-31006 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2022-31006?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2022-31006, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2022-31006

Explore →

Is Your Infrastructure Affected by CVE-2022-31006?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.