Klever-Go Account takeover: `kleverUpdateAccountPermission` authorizes on attacker-controlled `RecipientAddr` instead of the authenticated caller

[ Description ]Official description

Klever-Go is the Go implementation of the Klever blockchain protocol. Prior to 1.7.20, the KleverUpdateAccountPermission built-in authorizes replacement of a target account's permissions by checking attacker-controlled vmInput.RecipientAddr instead of authenticated vmInput.CallerAddr. An attacker-controlled contract can choose a victim account with configured permissions as RecipientAddr, and contractHasValidPermission can accept the victim's default self-signer as authorization. UpdatePermission can then replace the victim's entire permission set with attacker-supplied Owner permissions, enabling asset theft or permanent lockout without a victim key or signature. Accounts without stored permissions and the native transaction path are not affected. This issue is fixed in version 1.7.20.

[ Fixes ]Fixes and patches

• github.com/klever-io/klever-go 1.7.20Fixed version · GitHub Advisories · go package github.com/klever-io/klever-go: upgrade to 1.7.20 or later (affected <= 1.7.19)

[ Packages ]Affected open-source packages

• github.com/klever-io/klever-go goAffected <= 1.7.19 · fixed in 1.7.20 · GHSA-97cv-x867-6xhm

[ References ]References

• gist.github.com/mabdullah22/a41f90aa5ba86bbebf121f739bd5f5e9
• github.com/klever-io/klever-go/commit/c58740eb74d7ee8f07db1e18a7d6214b5559ba32
• github.com/klever-io/klever-go/releases/tag/v1.7.20
• github.com/klever-io/klever-go/security/advisories/GHSA-97cv-x867-6xhm