鱼皮AI导航
鱼皮AI导航
  • 主页
  • 社区
  • AI工具
  • AI知识库
  • AI提示词
  • MCP
  • Skills
  • AI学习资源
  • AI资讯
  • GitHub开源
登录/注册

cosmos-vulnerability-scanner

专注于 Cosmos SDK 区块链及 CosmWasm 智能合约的安全审计,精准识别可能导致链停摆、共识失败或资产损失的九类核心漏洞,涵盖非确定性行为、签名者校验错误、ABCI 异常崩溃、数值舍入偏差等关键风险点。

区块链
访问 GitHub
文档Skills.MD
name
cosmos-vulnerability-scanner
description
Scans Cosmos SDK blockchains for 9 consensus-critical vulnerabilities including non-determinism, incorrect signers, ABCI panics, and rounding errors. Use when auditing Cosmos chains or CosmWasm contracts. (project, gitignored)

Cosmos Vulnerability Scanner

1. Purpose

Systematically scan Cosmos SDK blockchain modules and CosmWasm smart contracts for platform-specific security vulnerabilities that can cause chain halts, consensus failures, or fund loss. This skill encodes 9 critical vulnerability patterns unique to Cosmos-based chains.

2. When to Use This Skill

  • Auditing Cosmos SDK modules (custom x/ modules)
  • Reviewing CosmWasm smart contracts (Rust)
  • Pre-launch security assessment of Cosmos chains
  • Investigating chain halt incidents
  • Validating consensus-critical code changes
  • Reviewing ABCI method implementations

3. Platform Detection

File Extensions & Indicators

  • Go files: .go, .proto
  • CosmWasm: .rs (Rust with cosmwasm imports)

Language/Framework Markers

▼
go
复制代码
// Cosmos SDK indicators import ( "github.com/cosmos/cosmos-sdk/types" sdk "github.com/cosmos/cosmos-sdk/types" "github.com/cosmos/cosmos-sdk/x/..." ) // Common patterns keeper.Keeper sdk.Msg, GetSigners() BeginBlocker, EndBlocker CheckTx, DeliverTx protobuf service definitions
▼
rust
复制代码
// CosmWasm indicators use cosmwasm_std::*; #[entry_point] pub fn execute(deps: DepsMut, env: Env, info: MessageInfo, msg: ExecuteMsg)

Project Structure

  • x/modulename/ - Custom modules
  • keeper/keeper.go - State management
  • types/msgs.go - Message definitions
  • abci.go - BeginBlocker/EndBlocker
  • handler.go - Message handlers (legacy)

Tool Support

  • CodeQL: Custom rules for non-determinism and panics
  • go vet, golangci-lint: Basic Go static analysis
  • Manual review: Critical for consensus issues

4. How This Skill Works

When invoked, I will:

  1. Search your codebase for Cosmos SDK modules
  2. Analyze each module for the 9 vulnerability patterns
  3. Report findings with file references and severity
  4. Provide fixes for each identified issue
  5. Check message handlers for validation issues

5. Example Output

When vulnerabilities are found, you'll get a report like this:

▼
text
复制代码
=== COSMOS SDK VULNERABILITY SCAN RESULTS === Project: my-cosmos-chain Files Scanned: 6 (.go) Vulnerabilities Found: 2 --- [CRITICAL] Incorrect GetSigners() --- ## 5. Vulnerability Patterns (9 Patterns) I check for 9 critical vulnerability patterns unique to CosmWasm. For detailed detection patterns, code examples, mitigations, and testing strategies, see [VULNERABILITY_PATTERNS.md](resources/VULNERABILITY_PATTERNS.md). ### Pattern Summary: 1. **Missing Denom Validation** ⚠️ CRITICAL - Accepting arbitrary token denoms 2. **Insufficient Authorization** ⚠️ CRITICAL - Missing sender/admin validation 3. **Missing Balance Check** ⚠️ HIGH - Not verifying sufficient balances 4. **Improper Reply Handling** ⚠️ HIGH - Unsafe submessage reply processing 5. **Missing Reply ID Check** ⚠️ MEDIUM - Not validating reply IDs 6. **Improper IBC Packet Validation** ⚠️ CRITICAL - Unvalidated IBC packets 7. **Unvalidated Execute Message** ⚠️ HIGH - Missing message validation 8. **Integer Overflow** ⚠️ HIGH - Unchecked arithmetic operations 9. **Reentrancy via Submessages** ⚠️ MEDIUM - State changes before submessages For complete vulnerability patterns with code examples, see [VULNERABILITY_PATTERNS.md](resources/VULNERABILITY_PATTERNS.md). ## 5. Scanning Workflow ### Step 1: Platform Identification 1. Identify Cosmos SDK version (`go.mod`) 2. Locate custom modules (`x/*/`) 3. Find ABCI methods (`abci.go`, BeginBlocker, EndBlocker) 4. Identify message types (`types/msgs.go`, `.proto`) ### Step 2: Critical Path Analysis Focus on consensus-critical code: - BeginBlocker / EndBlocker implementations - Message handlers (execute, DeliverTx) - Keeper methods that modify state - CheckTx priority logic ### Step 3: Non-Determinism Sweep **This is the highest priority check for Cosmos chains.** ```bash # Search for non-deterministic patterns grep -r "range.*map\[" x/ grep -r "\bint\b\|\buint\b" x/ | grep -v "int32\|int64\|uint32\|uint64" grep -r "float32\|float64" x/ grep -r "go func\|go routine" x/ grep -r "select {" x/ grep -r "time.Now()" x/ grep -r "rand\." x/

For each finding:

  1. Verify it's in consensus-critical path
  2. Confirm it causes non-determinism
  3. Assess severity (chain halt vs data inconsistency)

Step 4: ABCI Method Analysis

Review BeginBlocker and EndBlocker:

  • Computational complexity bounded?
  • No unbounded iterations?
  • No nested loops over large collections?
  • Panic-prone operations validated?
  • Benchmarked with maximum state?

Step 5: Message Validation

For each message type:

  • GetSigners() address matches handler usage?
  • All error returns checked?
  • Priority set in CheckTx if critical?
  • Handler registered (or using v0.47+ auto-registration)?

Step 6: Arithmetic & Bookkeeping

  • sdk.Dec operations use multiply-before-divide?
  • Rounding favors protocol over users?
  • Custom bookkeeping synchronized with x/bank?
  • Invariant checks in place?

6. Reporting Format

Finding Template

▼
markdown
复制代码
## [CRITICAL] Non-Deterministic Map Iteration in EndBlocker **Location**: `x/dex/abci.go:45-52` **Description**: The EndBlocker iterates over an unordered map to distribute rewards, causing different validators to process users in different orders and produce different state roots. This will halt the chain when validators fail to reach consensus. **Vulnerable Code**: ```go // abci.go, line 45 func EndBlocker(ctx sdk.Context, k keeper.Keeper) { rewards := k.GetPendingRewards(ctx) // Returns map[string]sdk.Coins for user, amount := range rewards { // NON-DETERMINISTIC ORDER k.bankKeeper.SendCoins(ctx, moduleAcc, user, amount) } }

Attack Scenario:

  1. Multiple users have pending rewards
  2. Different validators iterate in different orders due to map randomization
  3. If any reward distribution fails mid-iteration, state diverges
  4. Validators produce different app hashes
  5. Chain halts - cannot reach consensus

Recommendation: Sort map keys before iteration:

▼
go
复制代码
func EndBlocker(ctx sdk.Context, k keeper.Keeper) { rewards := k.GetPendingRewards(ctx) // Collect and sort keys for deterministic iteration users := make([]string, 0, len(rewards)) for user := range rewards { users = append(users, user) } sort.Strings(users) // Deterministic order // Process in sorted order for _, user := range users { k.bankKeeper.SendCoins(ctx, moduleAcc, user, rewards[user]) } }

References:

  • building-secure-contracts/not-so-smart-contracts/cosmos/non_determinism
  • Cosmos SDK docs: Determinism
▼
text
复制代码
--- ## 7. Priority Guidelines ### Critical - CHAIN HALT Risk - Non-determinism (any form) - ABCI method panics - Slow ABCI methods - Incorrect GetSigners (allows unauthorized actions) ### High - Fund Loss Risk - Missing error handling (bankKeeper.SendCoins) - Broken bookkeeping (accounting mismatch) - Missing message priority (oracle/emergency messages) ### Medium - Logic/DoS Risk - Rounding errors (protocol value leakage) - Unregistered message handlers (functionality broken) --- ## 8. Testing Recommendations ### Non-Determinism Testing ```bash # Build for different architectures GOARCH=amd64 go build GOARCH=arm64 go build # Run same operations, compare state roots # Must be identical across architectures # Fuzz test with concurrent operations go test -fuzz=FuzzEndBlocker -parallel=10

ABCI Benchmarking

▼
go
复制代码
func BenchmarkBeginBlocker(b *testing.B) { ctx := setupMaximalState() // Worst-case state b.ResetTimer() for i := 0; i < b.N; i++ { BeginBlocker(ctx, keeper) } // Must complete in < 1 second require.Less(b, b.Elapsed()/time.Duration(b.N), time.Second) }

Invariant Testing

▼
go
复制代码
// Run invariants in integration tests func TestInvariants(t *testing.T) { app := setupApp() // Execute operations app.DeliverTx(...) // Check invariants _, broken := keeper.AllInvariants()(app.Ctx) require.False(t, broken, "invariant violation detected") }

9. Additional Resources

  • Building Secure Contracts: building-secure-contracts/not-so-smart-contracts/cosmos/
  • Cosmos SDK Docs: https://docs.cosmos.network/
  • CodeQL for Go: https://codeql.github.com/docs/codeql-language-guides/codeql-for-go/
  • Cosmos Security Best Practices: https://github.com/cosmos/cosmos-sdk/blob/main/docs/docs/learn/advanced/17-determinism.md

10. Quick Reference Checklist

Before completing Cosmos chain audit:

Non-Determinism (CRITICAL):

  • No map iteration in consensus code
  • No platform-dependent types (int, uint, float)
  • No goroutines in message handlers/ABCI
  • No select statements with multiple channels
  • No rand, time.Now(), memory addresses
  • All serialization is deterministic

ABCI Methods (CRITICAL):

  • BeginBlocker/EndBlocker computationally bounded
  • No unbounded iterations
  • No nested loops over large collections
  • All panic-prone operations validated
  • Benchmarked with maximum state

Message Handling (HIGH):

  • GetSigners() matches handler address usage
  • All error returns checked
  • Critical messages prioritized in CheckTx
  • All message types registered

Arithmetic & Accounting (MEDIUM):

  • Multiply before divide pattern used
  • Rounding favors protocol
  • Custom bookkeeping synced with x/bank
  • Invariant checks implemented

Testing:

  • Cross-architecture builds tested
  • ABCI methods benchmarked
  • Invariants checked in CI
  • Integration tests cover all messages
区块链

快捷安装

复制到终端去安装 Skill

npxskillsaddtrailofbits/skills--skill"cosmos-vulnerability-scanner"
站长:程序员鱼皮 老鱼简历 商务合作 增值电信业务经营许可证
2026 鱼皮AI导航 | 沪ICP备19026706号-6
站长:程序员鱼皮 老鱼简历 商务合作 增值电信业务经营许可证
2026 鱼皮AI导航 | 沪ICP备19026706号-6
🔥热门工具
朱雀AI检测朱雀AI检测
朱雀AI检测助手朱雀AI检测助手
LovartLovart
老鱼简历老鱼简历
WritePass官网WritePass官网
面多多面多多
CursorCursor
星月写作星月写作
朱雀AI检测助手朱雀AI检测助手
零感AI零感AI
Skills 推荐
property-based-testing
通过生成随机输入验证代码在各类边界条件下的行为一致性,适用于序列化、解析、归一化及纯函数等场景,能有效发现隐含缺陷并提升测试覆盖率,尤其适合需要高可靠性的算法与智能合约验证。
compliance-checker
能够对基础设施配置进行合规性评估,检查是否符合 SOC2、HIPAA 和 PCI DSS 等行业标准,识别潜在的安全风险与违规项,并生成改进建议报告,适用于安全审计与合规审查场景。
orchestration
作为系统的核心协调中枢,负责将用户复杂需求拆解为并行任务流,动态调度不同能力的智能体协同工作,自动管理任务依赖与执行状态,并在后台静默完成多线程探索、分析与实现,最终整合结果交付完整解决方案。
skill-adapter
对基础设施配置进行多标准合规性评估,覆盖 SOC2、HIPAA 和 PCI DSS 等主流框架,自动识别配置偏差与安全风险,并生成可操作的整改建议报告,支撑持续合规治理与审计准备。
contract-test-creator
自动生成符合行业规范的契约测试代码与配置,提供从框架搭建到单元测试、集成测试及模拟对象编写的全流程支持,适用于需要实现高质量自动化测试验证的开发场景。