No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.
How severe is This vulnerability?
Low severity, with a CVSS score of 3.1, published 5 April 2024.
Which products and versions are affected?
github.com/cosmos/ibc-go (Go) SEMVER:introduced=0; github.com/cosmos/ibc-go/v2 (Go) SEMVER:introduced=0; github.com/cosmos/ibc-go/v3 (Go) SEMVER:introduced=0; github.com/cosmos/ibc-go/v4 (Go) SEMVER:introduced=0,fixed=4.6.0; and 4 more.
Is there a fix for This vulnerability?
Yes. github.com/cosmos/ibc-go/v4 (Go): upgrade to 4.6.0 or later; github.com/cosmos/ibc-go/v5 (Go): upgrade to 5.4.0 or later; github.com/cosmos/ibc-go/v6 (Go): upgrade to 6.3.0 or later; github.com/cosmos/ibc-go/v7 (Go): upgrade to 7.4.0 or later; github.com/cosmos/ibc-go/v8 (Go): upgrade to 8.2.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected?
Check whether you run github.com/cosmos/ibc-go (Go), github.com/cosmos/ibc-go/v2 (Go), github.com/cosmos/ibc-go/v3 (Go) or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
github.com/cosmos/ibc-go/v4 (Go): upgrade to 4.6.0 or later
go get github.com/cosmos/ibc-go/v4@v4.6.0
github.com/cosmos/ibc-go/v5 (Go): upgrade to 5.4.0 or later
go get github.com/cosmos/ibc-go/v5@v5.4.0
github.com/cosmos/ibc-go/v6 (Go): upgrade to 6.3.0 or later
go get github.com/cosmos/ibc-go/v6@v6.3.0
github.com/cosmos/ibc-go/v7 (Go): upgrade to 7.4.0 or later
go get github.com/cosmos/ibc-go/v7@v7.4.0
github.com/cosmos/ibc-go/v8 (Go): upgrade to 8.2.0 or later