github.com/klever-io/klever-go
Affected
- introduced
0, fixed1.7.17(semver)
Fixed versions
1.7.17
Fix
- Fixed version
1.7.17go get github.com/klever-io/[email protected]
Advisory
Also known as: GO-2026-5204
Klever-Go P2P MultiDataInterceptor leaks global throttler slots on malformed compressed batches (DoS)
Publisher note
Fixed in `v1.7.17`. Operators running < v1.7.17 should upgrade. The decompression-error path in MultiDataInterceptor.ProcessReceivedMessage now releases the global throttler slot before returning (guarded defer after StartProcessing(), disabled when the asynchronous goroutine takes ownership).
Patch commits on develop: 333f6ec9, 68b94a40 (merged from private fork klever-io/klever-go-ghsa-74m6-4hjp-7226).
This advisory was originally filed jointly with a separate KVM read-only isolation bypass; that finding is now tracked under GHSA-jc6w-wmfc-fh33 so each issue receives its own CVE.
The original disclosure from @LoGGGG240211 follows verbatim, including the embedded proof-of-concept source.
---
Private Vulnerability Report
Repository: klever-io/klever-go
Reviewed commit: 405d01b0abbf0d3e73b4a990bd7394a01f200dc2
Disclosure channel: GitHub Private Vulnerability Reporting
Reporter GitHub account: LoGGGG240211
2.1 MultiDataInterceptor malformed compressed batches permanently consume global P2P throttler slots
Severity : High
Confidence : HIGH
Attack Complexity : LOW
PoC Status : Confirmed
Description
The P2P MultiDataInterceptor starts throttled processing before it validates and decompresses a received batch. PreProcessMessage checks whether the global interceptor throttler can process the message and then calls StartProcessing(). After that point, ProcessReceivedMessage unmarshals the batch and enters the compressed-batch branch when b.IsCompressed is true. If b.Decompress() fails, the function logs the gzip error and returns immediately without calling EndProcessing().
This creates a permanent slot leak in the interceptor throttler. The normal successful path releases the slot only later in the asynchronous processing goroutine. Other validation error paths release the slot explicitly, but the decompression-error path does not. The impact is amplified because the same global throttler is shared by transaction multi-data interceptors, trie-node multi-data interceptors, and header interceptors. The hardcoded global capacity is 100, so a connected peer that can deliver 100 malformed compressed batch envelopes can cause later valid P2P interceptor processing on the affected node to fail with system busy until the process is restarted or the throttler state is otherwise reset.
Location
Preconditions
MultiDataInterceptor topic handler.Impact
Successful exploitation causes a persistent per-node denial of P2P interceptor processing until node restart or throttler reset. The affected throttler is shared across transaction batch processing and trie-node sync processing, and header processing also uses the same throttler. The PoC demonstrates the concrete effect with a capacity-2 throttler: two malformed compressed batches leak both slots and the third message returns system busy. In the reviewed codebase, the production factory hardcodes the shared capacity to 100, so the same condition is expected after approximately 100 malformed compressed batches. The impact is reversible by restarting the node or otherwise resetting the throttler state.
Exploit Cost
No gas and no protocol capital are required. The practical cost is the network cost of sending malformed compressed P2P batch messages to the target node, approximately 100 messages for the hardcoded production global capacity.
Steps to Reproduce
poc_mdi_throttler_slot_leak_test.go in an empty directory.GOTOOLCHAIN=go1.25.9 go test -v poc_mdi_throttler_slot_leak_test.go.StartProcessing() without incrementing EndProcessing() after a gzip decompression error.system busy on the third malformed compressed batch.Proof-of-Concept Result
Running GOTOOLCHAIN=go1.25.9 go test -v poc_mdi_throttler_slot_leak_test.go after dependency setup produces the following output. The result confirms that malformed compressed batches leak throttler slots and cause a real throttler to reject later processing as system busy.
=== RUN TestPoC_MalformedCompressedBatchLeaksThrottlerSlot
ERROR[2026-04-28 13:35:04.398] MultiDataInterceptor.ProcessReceivedMessage err = gzip: invalid header
poc_mdi_throttler_slot_leak_test.go:108: process_error=gzip: invalid header
poc_mdi_throttler_slot_leak_test.go:109: start_count_before=0
poc_mdi_throttler_slot_leak_test.go:110: start_count_after=1
poc_mdi_throttler_slot_leak_test.go:111: end_count_before=0
poc_mdi_throttler_slot_leak_test.go:112: end_count_after=0
ERROR[2026-04-28 13:35:04.398] MultiDataInterceptor.ProcessReceivedMessage err = gzip: invalid header
ERROR[2026-04-28 13:35:04.398] MultiDataInterceptor.ProcessReceivedMessage err = gzip: invalid header
poc_mdi_throttler_slot_leak_test.go:133: real_throttler_attempt_1=gzip: invalid header
poc_mdi_throttler_slot_leak_test.go:134: real_throttler_attempt_2=gzip: invalid header
poc_mdi_throttler_slot_leak_test.go:135: real_throttler_attempt_3=system busy
--- PASS: TestPoC_MalformedCompressedBatchLeaksThrottlerSlot (0.00s)
PASS
ok command-line-arguments 0.002sHigh Basis: The source's own band: HIGH
0, fixed 1.7.17 (semver)1.7.17
1.7.17go get github.com/klever-io/[email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0