Summary
Barberry Security Advisory - regarding x/auth periodic vesting accounts
Workarounds
There is no workaround for this issue. Upgrade immediately.
References
- Patched versions release notes: v0.47.3, v0.46.13.
- Forum Post
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.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
>= 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.
Frequently Asked Questions
- What is GHSA-J2CR-JC39-WPX5? GHSA-J2CR-JC39-WPX5 is a medium-severity security vulnerability in github.com/cosmos/cosmos-sdk (go), affecting versions >= 0.46.0, <= 0.46.12. It is fixed in 0.46.13, 0.47.3.
- Which versions of github.com/cosmos/cosmos-sdk are affected by GHSA-J2CR-JC39-WPX5? github.com/cosmos/cosmos-sdk (go) versions >= 0.46.0, <= 0.46.12 is affected.
- Is there a fix for GHSA-J2CR-JC39-WPX5? Yes. GHSA-J2CR-JC39-WPX5 is fixed in 0.46.13, 0.47.3. Upgrade to this version or later.
- Is GHSA-J2CR-JC39-WPX5 exploitable, and should I be worried? Whether GHSA-J2CR-JC39-WPX5 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether GHSA-J2CR-JC39-WPX5 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix GHSA-J2CR-JC39-WPX5?
- Upgrade
github.com/cosmos/cosmos-sdkto 0.46.13 or later - Upgrade
github.com/cosmos/cosmos-sdkto 0.47.3 or later
- Upgrade