# GHSA-95rx-m9m5-m94v: ASA-2024-006: ValidateVoteExtensions helper function in Cosmos SDK may allow incorrect voting power assumptions

> A dishonest proposer can manipulate voting power assumptions in Cosmos SDK chains, potentially altering state and elevating privileges.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 12 Mar 2024
- **Also known as:** GO-2024-2638

## What is GHSA-95rx-m9m5-m94v?

GHSA-95rx-m9m5-m94v is a vulnerability in github.com/cosmos/cosmos-sdk, published on 12 Mar 2024. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

## ASA-2024-006: ValidateVoteExtensions helper function may allow incorrect voting power assumptions

**Component**: Cosmos SDK
**Criticality**: High
**Affected Versions**: Cosmos SDK versions <= 0.50.4, on 0.50 branches
**Affected Users**: Chain developers, Validator and Node operators
**Impact**: Elevation of Privilege

## Summary

The default `ValidateVoteExtensions` helper function infers total voting power based off of the injected `VoteExtension`, which are injected by the proposer.  If your chain utilizes the `ValidateVoteExtensions` helper in `ProcessProposal`, a dishonest proposer can potentially mutate voting power of each validator it includes in the injected `VoteExtension`, which could have potentially unexpected or negative consequences on modified state.  Additional validation on injected `VoteExtension` data was added to confirm voting power against the state machine.

## Next Steps for Impacted Parties

If you are a chain developer on an affected version of the Cosmos SDK, it is advised to update to the latest available version of the Cosmos SDK for your project.  Once a patched version is available, it is recommended that network operators upgrade.

A Github Security Advisory for this issue is available in the Cosmos-SDK [repository](https://github.com/cosmos/cosmos-sdk/security/advisories/GHSA-95rx-m9m5-m94v). For more information about Cosmos SDK, see https://docs.cosmos.network/.

## Which versions are affected by GHSA-95rx-m9m5-m94v?

3 open source packages ship an affected version, including github.com/cosmos/cosmos-sdk.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/cosmos/cosmos-sdk` | Go | From 0.50.0 | 0.50.5 |
| `github.com/cosmos/cosmos-sdk` | Go | From 0.50.0 | 0.50.5 |
| `github.com/cosmos/cosmos-sdk` | Go | From 0.50.0 | 0.50.5 |

## How do I fix GHSA-95rx-m9m5-m94v?

Upgrade github.com/cosmos/cosmos-sdk to 0.50.5 or later.

## Is GHSA-95rx-m9m5-m94v being exploited?

There is no known exploitation of GHSA-95rx-m9m5-m94v in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-95rx-m9m5-m94v and fix it if it is affected.

What it is: GHSA-95rx-m9m5-m94v is a vulnerability in github.com/cosmos/cosmos-sdk, published on 12 Mar 2024. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-95rx-m9m5-m94v in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/cosmos/cosmos-sdk (Go): affected from 0.50.0; fixed in 0.50.5
- github.com/cosmos/cosmos-sdk (Go): affected from 0.50.0; fixed in 0.50.5
- github.com/cosmos/cosmos-sdk (Go): affected from 0.50.0; fixed in 0.50.5

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/GHSA-95rx-m9m5-m94v/ (Markdown: https://insights.sbomify.com/GHSA-95rx-m9m5-m94v/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-95rx-m9m5-m94v

---
From sbomify Insights: https://insights.sbomify.com/GHSA-95rx-m9m5-m94v/
Summaries are generated and may contain mistakes; the official description above is the record.