Klever-Go
Klever-Go: Elasticsearch bulk / painless injection via on-chain account name -> explorer/indexer data forgery
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.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 1.7.20
Fixed in 1.7.20
Mitigation
Upgrade klever-go to 1.7.20 or later.
References
- Vendor advisory github.com/klever-io/klever-go/security/adviso…
- Patch github.com/klever-io/klever-go/commit/f0036676…
- Patch github.com/klever-io/klever-go/commit/f54ea730…
1 more
- Release notes github.com/klever-io/klever-go/releases/tag/v1…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.