CyberRota Analysis
AI-GeneratedVersions 1.7.14 to 1.7.17 of the Klever-Go implementation of the Klever blockchain protocol are vulnerable to a denial of service attack due to improper handling of incoming HTTP request headers, allowing unauthenticated clients to exhaust server resources. This vulnerability can lead to the REST API becoming unavailable to legitimate users when exposed beyond localhost, particularly in Docker deployments. Organizations using affected versions should prioritize upgrading to version 1.7.18 to mitigate this risk.
Public Exploit Signal
A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.
Note: these links are listed for security research and verification purposes only.
Original NVD Description
Klever-Go is the Go implementation of the Klever blockchain protocol. Versions from 1.7.14 through 1.7.17 are vulnerable to a remotely triggerable denial of service. Both REST APIs are started with the Gin Engine.Run convenience method, which serves requests through Go's default HTTP server with no ReadHeaderTimeout, ReadTimeout, or MaxHeaderBytes configured. As a result, incoming connections that never complete their request headers are held open indefinitely. When a REST listener is reachable beyond localhost through the documented all-interface bind or a Docker port-publish deployment, a single unauthenticated client can open many slow-header connections and hold them open until server file descriptors are exhausted, preventing the API from accepting new connections. This renders the REST API unavailable to legitimate clients. This issue is fixed in version 1.7.18.