Skip to content
Fencer Intel
high —

GHSA-4jmp-x7mh-rgmr json

Finality Provider vulnerable to anti-slashing bypassing due to misconfiguration

published 11mo ago modified 8mo ago also GO-2025-4236

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

The anti-slashing is not effective if the attacker can access EOTS manager endpoints.

### Impact

If the EOTS manager endpoints are open to public without HMAC protection, the attacker can manually cause slashing of the finality provider through the RPC endpoints.

Report credits go to: x.com/RebelsRunways

Patch / fix

  • go github.com/babylonlabs-io/finality-provider 1.0.4

Is GHSA-4jmp-x7mh-rgmr 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 Fencer

Affected packages

ecosystem package affected fixed in
go github.com/babylonlabs-io/finality-provider
<1.0.4
1 listed version
all versions
1.0.4

Classification

Weakness

References

Sources

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.