You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The following distinct but related vulnerabilities have been identified and manually verified by the team.
BlockedAddress Input Validation: This issue involves insufficient validation mechanisms for BlockedAddress entries. The lack of rigorous validation allows for the potential misuse of blockchain resources, compromising the security of transactions.
Sanity Checks for PeriodicVestingAccount: In msg_server.go, this vulnerability arises from inadequate sanity checks during the creation of a PeriodicVestingAccount. Specifically, the system does not correctly handle cases where EndTime values are negative or overflow, which can result in system crashes or undefined behavior.
Faulty GRPC Query Tally: In grpc_query.go, the query for a failed proposal tally incorrectly attempts to tally votes anew instead of fetching the final tally result from proposal.FinalTallyResult, after votes have been removed post-failure. This results in inaccurate or impossible query responses.
Recommendation
The vesting module should refer to the correct upstream repository of cosmossdk/x/auth/vesting to ensure all security patches are correctly applied.
Note
Severity: Medium
target: v7.1.0 - Commit: 3c854270b006db30aa3894da2cdba10cc31b8c5f
Ref: OKP4 Blockchain Audit Report v1.0 - 02-05-2024 - BlockApex
Description
The following distinct but related vulnerabilities have been identified and manually verified by the team.
PeriodicVestingAccount
: Inmsg_server.go
, this vulnerability arises from inadequate sanity checks during the creation of aPeriodicVestingAccount
. Specifically, the system does not correctly handle cases whereEndTime
values are negative or overflow, which can result in system crashes or undefined behavior.grpc_query.go
, the query for a failed proposal tally incorrectly attempts to tally votes anew instead of fetching the final tally result from proposal.FinalTallyResult, after votes have been removed post-failure. This results in inaccurate or impossible query responses.Recommendation
The vesting module should refer to the correct upstream repository of
cosmossdk/x/auth/vesting
to ensure all security patches are correctly applied.References
The text was updated successfully, but these errors were encountered: