# Indy's NODE_UPGRADE transaction vulnerable to remote code execution

Advisory record · `GHSA-r6v9-p59m-gj2p`

- **Identifiers:** `GHSA-r6v9-p59m-gj2p` · `CVE-2022-31020` · `PYSEC-2022-265`
- **State:** Confirmed
- **Severity:** CVSS 8.8 High
- **Critical:** No
- **Weakness (CWE):** [CWE-20](https://cwe.mitre.org/data/definitions/20.html) · [CWE-287](https://cwe.mitre.org/data/definitions/287.html)
- **Tags:** [Authentication bypass](https://agentprime.io/advisories/tag/auth-bypass.md) · [CWE-20](https://agentprime.io/advisories/tag/cwe-20.md)
- **Published:** 2 Sept 2022
- **Updated:** 23 Nov 2024
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 2 Sept 2022, 21:55 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `indy-node` (PyPI): affected `<1.12.5rc1`; fixed in `1.12.5rc1`

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 8.8 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.023, the 83rd percentile, on 21 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

This record came from the full history of the GitHub Advisory Database, published 2 Sept 2022. New records show when each source confirmed them.

## Sources

- [GitHub Advisory Database: GHSA-r6v9-p59m-gj2p](https://github.com/advisories/GHSA-r6v9-p59m-gj2p)
- [OSV: GHSA-r6v9-p59m-gj2p](https://osv.dev/vulnerability/GHSA-r6v9-p59m-gj2p)
- <https://github.com/hyperledger/indy-node/security/advisories/GHSA-r6v9-p59m-gj2p>
- <https://nvd.nist.gov/vuln/detail/CVE-2022-31020>
- <https://github.com/hyperledger/indy-node/commit/fe507474f77084faef4539101e2bbb4d508a97f5>
- <https://github.com/hyperledger/indy-node>
- <https://github.com/hyperledger/indy-node/releases/tag/v1.12.5>
- <https://github.com/pypa/advisory-database/tree/main/vulns/indy-node/PYSEC-2022-265.yaml>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-r6v9-p59m-gj2p>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-r6v9-p59m-gj2p/>. Everything for agents: <https://agentprime.io/llms.txt>.
