# CVE-2023-1944: [minikube] ssh server with default password

> Attackers can gain SSH access to minikube containers using a default password, leading to potential code execution and privilege escalation.

- **Severity:** High 8.4 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 May 2023
- **Updated:** 16 Jan 2025
- **Also known as:** GHSA-88g7-jhqx-q9gp

## What is CVE-2023-1944?

CVE-2023-1944 is a high-severity vulnerability in Kubernetes minikube, published on 24 May 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

This vulnerability enables ssh access to minikube container using a default password.

Weakness: CWE-798 (Use of Hard-coded Credentials), CWE-259 (Use of Hard-coded Password)

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

It affects 1 product.


Products: Kubernetes Minikube.

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

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

## Is CVE-2023-1944 being exploited?

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

## Other vulnerabilities in Kubernetes minikube

- [CVE-2023-1174](https://insights.sbomify.com/CVE-2023-1174/): [minikube] Network Port exposure in minikube running on macOS using Docker driver (critical 9.8)
- [CVE-2018-1002103](https://insights.sbomify.com/CVE-2018-1002103/): Minikube RCE via DNS Rebinding (high 8.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-1944 is a high-severity vulnerability in Kubernetes minikube, published on 24 May 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-1944 in the wild and no public exploit code.

Affected product: Kubernetes minikube. 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-1944/ (Markdown: https://insights.sbomify.com/CVE-2023-1944/index.md)
```

## Sources

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

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