Node crash via fatal not-leader RPC handling
Published Apr 13, 2023 · Updated Feb 7, 2025
Denial of service in TiKV 6.1.2 allows remote attackers to crash a starting node when an RPC context deadline is exceeded. The startup path at server.rs:955 treats a gRPC UNAVAILABLE not-leader response as a fatal error rather than a transient condition. Reproduction requires node startup during kill, pause, or partition fault injection; the demonstrated consequence is termination of that node.
Summary
What happened
Denial of service in TiKV 6.1.2 allows remote attackers to crash a starting node when an RPC context deadline is exceeded. The startup path at server.rs:955 treats a gRPC UNAVAILABLE not-leader response as a fatal error rather than a transient condition. Reproduction requires node startup during kill, pause, or partition fault injection; the demonstrated consequence is termination of that node.
The record
- CVE
- CVE-2023-30636
- Published
- Apr 13, 2023
- Updated
- Feb 7, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-770, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 13, 2023CVE publishedPublication date reported by the CVE source.
- Feb 7, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- TiKV node-start failure reproductionproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo