# CVE-2023-30450: Misconfiguration in n/a

> Redpanda mishandles TLS configuration fields, potentially leaving broker RPC ports unencrypted unless manually reconfigured while the cluster is offline.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Apr 2023
- **Updated:** 12 Feb 2025
- **Also known as:** GHSA-x3pf-j9xx-29g6

## What is CVE-2023-30450?

CVE-2023-30450 is a medium-severity vulnerability in n/a, published on 8 Apr 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2023-30450?

It affects 1 product.


Products: Redpanda Redpanda.

## How do I fix CVE-2023-30450?

No fix has been published for CVE-2023-30450 yet. Limit exposure of the affected software until one is available.

## Is CVE-2023-30450 being exploited?

There is no known exploitation of CVE-2023-30450 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2023-50976](https://insights.sbomify.com/CVE-2023-50976/): Missing authorization in n/a (critical 9.8)
- [CVE-2023-24619](https://insights.sbomify.com/CVE-2023-24619/): Information disclosure in n/a (medium 5.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-30450 and fix it if it is affected.

What it is: CVE-2023-30450 is a medium-severity vulnerability in n/a, published on 8 Apr 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-30450 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-30450/ (Markdown: https://insights.sbomify.com/CVE-2023-30450/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-30450
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-30450
- OSV: https://osv.dev/vulnerability/CVE-2023-30450

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-30450/
Summaries are generated and may contain mistakes; the official description above is the record.