CyberRota Analysis
AI-GeneratedThe Klever-Go blockchain protocol prior to version 1.7.19 contains a vulnerability in the processPercentageRoyaltiesTransfer function, which allows a malicious user to exploit a 100% transfer percentage to mint KDA tokens without debiting the source account, leading to unbounded inflation of the token supply. This flaw primarily impacts KDA owners who configure royalty transfers, as it enables unauthorized asset transfers and undermines the integrity of the royalty system. Organizations utilizing this blockchain protocol should prioritize upgrading to version 1.7.19 to mitigate the risk of exploitation.
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.19, processPercentageRoyaltiesTransfer in core/kapp/accounts/accounts.go calls SubFromBalance after the split loop and after the royaltiesToPay <= 0 early return. computeSplitRoyalties rejects only when splitToPay > royaltiesToPay, so a valid PercentTransferPercentage = 10000 split consumes exactly 100 percent of the royalty pool, sets royaltiesToPay to zero, and returns before the source account is debited. The split recipient receives the full royaltyAmount while the sender pays nothing and the supply counter is not updated, allowing unbounded off-the-books inflation of the transferred KDA. A KDA owner must configure a TransferPercentage royalty with a 100 percent split, after which any holder's transfer of the asset triggers the mint; the sibling processFixedRoyaltiesTransfer path is not affected because it debits the source before distribution. This issue is fixed in version 1.7.19.