CyberRota Analysis
AI-GeneratedThe Klever-Go blockchain protocol is vulnerable due to improper authorization in the KleverUpdateAccountPermission built-in, allowing attackers to manipulate account permissions by exploiting the vmInput.RecipientAddr field. This flaw can lead to asset theft or permanent lockout of victim accounts, making it critical for users and developers of Klever-Go prior to version 1.7.20 to prioritize immediate updates to version 1.7.20 or later.
Public Exploit Signal
A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.
Note: these links are listed for security research and verification purposes only.
Original NVD 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.