GHSA-56j4-446m-qrf6 json
Babylon vulnerable to chain half when transaction has fees different than `ubbn`
published last yr. modified 8mo ago also GO-2025-3791
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no score, EPSS covers CVEs only
- public exploits
- 0
- none known
Summary
### Summary
Sending transactions with fees different than native Babylon genesis denom (`ubbn`) leads to chain halt.
### Impact
Denial of Service - Due to panic in the `x/distribution` module `BeginBlocker` triggered by a error when sending fees from `feeCollector` to `x/distribution` module - https://github.com/cosmos/cosmos-sdk/blob/main/x/distribution/keeper/allocation.go#L28 Babylon Genesis will halt
Patch / fix
Is GHSA-56j4-446m-qrf6 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerAffected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/babylonlabs-io/babylon/v2 | <2.2.0 |
2.2.0 |
| go | github.com/babylonlabs-io/babylon | <=1.1.0 all versions |
no fix listed |
Classification
- Weakness
-
- CWE-755 Improper Handling of Exceptional Conditions
References
-
github.com
/babylonlabs-io/babylon/commit/fe67aebd5216e7d3afa1d7dee2a3f82e548556f3
web, patch
-
github.com
/babylonlabs-io/babylon/security/advisories/GHSA-56j4-446m-qrf6
web, advisory
-
github.com
/babylonlabs-io/babylon
package
-
github.com
/cosmos/cosmos-sdk/blob/main/x/distribution/keeper/allocation.go#L28
web
Sources
- GitHub Advisory GHSA-56j4-446m-qrf6
- OSV GO-2025-3791
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.