Klever-Go: Elasticsearch bulk / painless injection via on-chain account name -> explorer/indexer data forgery

[ Why it matters ]Priority signals

• Public proof-of-concept exploit exists (CISA SSVC)

[ Description ]Official description

Klever-Go is the Go implementation of the Klever blockchain protocol. Prior to 1.7.20, indexer/common.go serializedDataForUpdateAccounts places the attacker-controlled acc.Name value into an Elasticsearch _bulk JSON and NDJSON request without escaping it. The SetAccountName transaction accepts valid UTF-8 account names containing quotes, backslashes, and newlines, and the resulting name is stored in consensus account state. When an indexer processes the account, those characters can break the JSON string, reject a bulk batch, or inject additional bulk actions that create, overwrite, or delete documents in indices writable by the indexer. The persistent state value is replayed by new or historical indexers, and direct access to the indexing host or Elasticsearch port is not required. This issue is fixed in version 1.7.20.

[ Fixes ]Fixes and patches

• github.com/klever-io/klever-go 1.7.20Fixed version · GitHub Advisories · go package github.com/klever-io/klever-go: upgrade to 1.7.20 or later (affected <= 1.7.19)

[ Packages ]Affected open-source packages

• github.com/klever-io/klever-go goAffected <= 1.7.19 · fixed in 1.7.20 · GHSA-7c7c-373r-gfjj

[ References ]References

• github.com/klever-io/klever-go/commit/f00366768b24be18fa7ae9de2e1905caa8b350af
• github.com/klever-io/klever-go/commit/f54ea730cc80a3ba4f906586a7d221b281548190
• github.com/klever-io/klever-go/releases/tag/v1.7.20
• github.com/klever-io/klever-go/security/advisories/GHSA-7c7c-373r-gfjj