How severe is GHSA-j2cr-jc39-wpx5?

No CVSS score has been assigned to GHSA-j2cr-jc39-wpx5 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-j2cr-jc39-wpx5?

GHSA-j2cr-jc39-wpx5 affects the following packages: github.com/cosmos/cosmos-sdk (Go), github.com/cosmos/cosmos-sdk (Go). Ecosystems affected: Go.

How do I fix GHSA-j2cr-jc39-wpx5?

Update github.com/cosmos/cosmos-sdk to 0.46.13 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-j2cr-jc39-wpx5 is resolved across your whole dependency graph.

How do I detect GHSA-j2cr-jc39-wpx5 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/cosmos/cosmos-sdk, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-j2cr-jc39-wpx5 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-j2cr-jc39-wpx5 actively exploited in the wild?

No public exploit code has been indexed for GHSA-j2cr-jc39-wpx5 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-j2cr-jc39-wpx5 published, and has it been updated?

GHSA-j2cr-jc39-wpx5 was published on July 7, 2023 and was last updated on November 8, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

Not in CISA KEV

Barberry Security Advisory - regarding x/auth periodic vesting accountsGHSA-j2cr-jc39-wpx5

Fix: cosmos/cosmos-sdk#16466

GHSA-j2cr-jc39-wpx5 is a security vulnerability in github.com/cosmos/cosmos-sdk. A fix is available for github.com/cosmos/cosmos-sdk — see the affected versions and patch details below.

Also known asGHSA-w44m-8mv2-v78hGO-2023-1861

Published

Jul 7, 2023

Updated

Nov 8, 2023

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Nov 8, 2023 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

2 pkgs affected

🐹github.com/cosmos/cosmos-sdk🐹github.com/cosmos/cosmos-sdk

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

Impact

In PeriodicVestingAccount, defined in x/auth, an attacker can initialize a victim's account as a malicious vesting account, which allows deposits but does not allow withdrawals. When the user then deposits funds into their account, those funds are locked forever, and the user is not able to withdraw them.

Patches

>= v0.46.13 for Cosmos SDK v0.46.x >= v0.47.3 for Cosmos SDK v0.47.x

If a network backported periodic vesting accounts to earlier versions of the SDK, those networks are affected too.

Workarounds

There is no workaround for this issue. Upgrade immediately.

References

Patched versions release notes: v0.47.3, v0.46.13.
Forum Post

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/cosmos/cosmos-sdk`	≥ 0.46.0&&< 0.46.13	0.46.13`go get github.com/cosmos/cosmos-sdk@v0.46.13`
🐹Go	`github.com/cosmos/cosmos-sdk`	≥ 0.47.0&&< 0.47.3	0.47.3`go get github.com/cosmos/cosmos-sdk@v0.47.3`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/cosmos/cosmos-sdk, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/cosmos/cosmos-sdk to 0.46.13 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-j2cr-jc39-wpx5 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

### Impact In `PeriodicVestingAccount`, defined in `x/auth`, an attacker can initialize a victim's account as a malicious vesting account, which allows deposits but does not allow withdrawals. When the user then deposits funds into their account, those funds are locked forever, and the user is not able to withdraw them. ### Patches \>= v0.46.13 for Cosmos SDK v0.46.x \>= v0.47.3 for Cosmos SDK v0.47.x If a network backported periodic vesting accounts to earlier versions of the SDK, those networks are affected too. ### Workarounds There is no workaround for this issue. Upgrade immediately