Files
nick-doc/Issues/ISSUE-107-scanner-tronGrid-pagination-next-url-used-unvalidated.md
Siavash Sameni dceaf82934 audit: 2026-05-30 full-codebase audit — report, issues, docs, runbooks
Full-codebase-audit 2026-05-30 outputs:
- Audit report: 09 - Audits/Full Codebase Audit - 2026-05-30.md
- 81 issue files ISSUE-055..135 (decisions + 1 skipped no-brainer).
- Scanner docs from scratch (was zero): architecture, data model, API ref, payment
  flow, operations runbook + repo README.
- Doc-sync updates across API reference, data models, flows, design system.
- Secret Rotation Runbook (08 - Operations) for the exposed credentials.
- Reusable workflow guide (07 - Development) + .claude/workflows/full-codebase-audit.js.

Issues remain status:open intentionally — the code fixes are uncommitted-then-committed
working-tree changes per repo and aren't "resolved" until merged/deployed.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-05-30 18:48:04 +04:00

1.1 KiB

issue, title, severity, domain, labels, status, created, source
issue title severity domain labels status created source
107 Scanner: TronGrid pagination next-URL used unvalidated — SSRF via API response medium Scanner
security
scanner
ssrf
open 2026-05-30 Full Codebase Audit 2026-05-30

Scanner: TronGrid pagination next-URL used unvalidated — SSRF via API response

Severity: medium Domain: Scanner Labels: security, scanner, ssrf

Description

scanner/tron_chain.go:180 follows the Links.Next URL from a TronGrid API response without validating that it has the same scheme and host as the configured RPC URL. A compromised or malicious TronGrid response can redirect the scanner to arbitrary internal endpoints.

Options

  1. Require next URL to share scheme+host with chain.RpcURL.
  2. Reconstruct pagination params ourselves instead of trusting Links.Next.
  3. Allowlist the TronGrid host.

Recommendation

Validate scheme+host equals the configured RPC URL before following Links.Next.

Affected Files

  • scanner/tron_chain.go:180

References