Broker RPC TLS disablement via array coercion
Published Apr 8, 2023 · Updated Feb 12, 2025
Improper configuration handling in Redpanda before 23.1.2 allows attackers to leave broker RPC traffic without TLS. The rpk YAML decoder coerces redpanda.rpc_server_tls into an array-backed field and writes that representation back, although brokers read the setting as an object. The condition requires rpk to process a configuration containing the field; affected clusters can retain unencrypted broker RPC until an offline configuration repair.
Summary
What happened
Improper configuration handling in Redpanda before 23.1.2 allows attackers to leave broker RPC traffic without TLS. The rpk YAML decoder coerces redpanda.rpc_server_tls into an array-backed field and writes that representation back, although brokers read the setting as an object. The condition requires rpk to process a configuration containing the field; affected clusters can retain unencrypted broker RPC until an offline configuration repair.
The record
- CVE
- CVE-2023-30450
- Published
- Apr 8, 2023
- Updated
- Feb 12, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-20
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 8, 2023CVE publishedPublication date reported by the CVE source.
- Feb 12, 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.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
No public exploit references are available in this record.
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