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.
{
"cna_assigner": "mitre",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2023/30xxx/CVE-2023-30450.json"
}{
"extracted_events": [
{
"cpe": "cpe:2.3:a:redpanda:redpanda:*:*:*:*:*:*:*:*",
"range": [
{
"introduced": "0"
},
{
"fixed": "23.1.2"
}
],
"source": "CPE_RANGE"
},
{
"range": [
{
"fixed": "58795aa07e88e0a63cebf4e1d9fcc717ceef0557"
}
],
"source": "REFERENCES_COMMIT"
},
{
"range": [
{
"fixed": "a839056381ea7cd71e68495854e388daf7a08ba7"
}
],
"source": "REFERENCES_COMMIT"
},
{
"range": [
{
"fixed": "cf82b99457e2434d3674e424ab560fe201e6c365"
}
],
"source": "REFERENCES_COMMIT"
}
]
}