CVE-2023-30450
Redpanda vulnerability
rpk in Redpanda before 23.1.2 mishandles the redpanda.rpc_server_tls field, leading to (for example) situations in which there is a data type mismatch that cannot be automatically fixed by rpk, and instead a user must reconfigure (while a cluster is turned off) in order to have TLS on broker RPC ports. NOTE: the fix was also backported to the 22.2 and 22.3 branches.
Affected products
Redpanda. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Redpanda runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- github.com/redpanda-data/redpanda/commit/58795aa07e88e0a63cebf4e1d9fcc717ceef0557 · Patch
- github.com/redpanda-data/redpanda/commit/a839056381ea7cd71e68495854e388daf7a08ba7 · Patch
- github.com/redpanda-data/redpanda/commit/cf82b99457e2434d3674e424ab560fe201e6c365 · Patch
- github.com/redpanda-data/redpanda/pull/7719 · Patch
- github.com/redpanda-data/redpanda/compare/v23.1.1...v23.1.2
- nvd.nist.gov/vuln/detail/CVE-2023-30450
- cve.org/CVERecord?id=CVE-2023-30450
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.