Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-w342-mj6g-v9c4 | Klever-Go KVM: Hash-array amplification in P2P resolver request handling |
Fri, 07 Aug 2026 23:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Klever-io
Klever-io klever-go |
|
| Vendors & Products |
Klever-io
Klever-io klever-go |
Fri, 07 Aug 2026 22:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Klever-Go is the Go implementation of the Klever blockchain protocol. Prior to 1.7.18, the P2P resolver request handling logic is vulnerable to hash-array amplification. A connected peer can send a compressed RequestDataType_HashArrayType direct request that is only 442 bytes on the wire but expands into 200,000 decoded hash entries inside the resolver path. The resolver's antiflood logic counts only a single logical message and the compressed wire size, and while Batch.Decompress() caps the decompressed byte size, it never limits the number of decoded repeated-field items. As a result, both TxResolver and TrieNodeResolver preallocate and iterate over the entire unchecked set of decoded hashes, causing remote memory and CPU amplification against any node that accepts P2P peer connections. This issue is fixed in version 1.7.18. | |
| Title | Klever-Go KVM: Hash-array amplification in P2P resolver request handling | |
| Weaknesses | CWE-400 | |
| References |
| |
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-08-07T22:09:03.931Z
Reserved: 2026-05-18T22:54:18.273Z
Link: CVE-2026-47249
No data.
No data.
No data.
OpenCVE Enrichment
Updated: 2026-08-07T23:30:17Z
-
CWE-400
Uncontrolled Resource Consumption
Github GHSA