Security Resilience

CVE-2023-1944

Exposed Creds in Kubernetes Minikube ≤ 1.29.0

Published
24 May 2023
Modified
21 November 2024
Patch / advisory
CVSS Score v3.1 8.4
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.0021 12th percentile
Risk Priority 60 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS, Forum of Incident Response and Security Teams (FIRST), epss.first.org. Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2023-1944 is a high-severity Use of Hard-coded Password (CWE-259) vulnerability in Kubernetes Minikube. Its CVSS base score is 8.4 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Valid Accounts (T1078); ranked at the 12th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

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

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

MITRE ATT&CK v20.0

T1021.004 SSH Lateral Movement
Adversaries may use [Valid Accounts](https://attack.
T1078 Valid Accounts Stealth
Adversaries may obtain and abuse credentials of existing accounts as a means of gaining Initial Access, Persistence, Privilege Escalation, or Defense Evasion.
T1078.001 Default Accounts Stealth
Adversaries may obtain and abuse credentials of a default account as a means of gaining Initial Access, Persistence, Privilege Escalation, or Defense Evasion.
T1078.002 Domain Accounts Stealth
Adversaries may obtain and abuse credentials of a domain account as a means of gaining Initial Access, Persistence, Privilege Escalation, or Defense Evasion.
T1078.003 Local Accounts Stealth
Adversaries may obtain and abuse credentials of a local account as a means of gaining Initial Access, Persistence, Privilege Escalation, or Defense Evasion.
T1078.004 Cloud Accounts Stealth
Valid accounts in cloud environments may allow adversaries to perform actions to achieve Initial Access, Persistence, Privilege Escalation, or Defense Evasion.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-14126Shared CWE-259, CWE-798
CVE-2025-2343Shared CWE-259, CWE-798
CVE-2024-4996Shared CWE-259, CWE-798
CVE-2024-11630Shared CWE-259, CWE-798
CVE-2025-9778Shared CWE-259, CWE-798
CVE-2026-112146Shared CWE-259, CWE-798
CVE-2025-8730Shared CWE-259, CWE-798
CVE-2025-5379Shared CWE-259, CWE-798
CVE-2024-39585Shared CWE-259, CWE-798
CVE-2026-19901Shared CWE-259, CWE-798

Affected Assets

kubernetes
minikube
≤ 1.29.0

Mitigating Controls

Likely Mitigating Controls

Our mappings. Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.

addresses: CWE-259 CWE-798

Changing default authenticators prior to first use directly prevents use of hard-coded passwords.

addresses: CWE-798 CWE-259

Intelligence programs surface reports of campaigns that abuse hard-coded credentials in products, prompting removal or replacement and thereby reducing successful exploitation.

addresses: CWE-798 CWE-259

Vetting reduces the chance a developer will deliberately insert hard-coded credentials as a backdoor or unauthorized access mechanism.

addresses: CWE-798 CWE-259

Supplier risk reviews identify and discourage hard-coded credentials in delivered products or services.

addresses: CWE-798

Enables users to notice when hard-coded credentials have been exploited for unauthorized access.

addresses: CWE-798

Security training explicitly warns against hard-coded credentials, lowering their use in systems.

addresses: CWE-798

Policy and procedures prohibit hard-coded credentials in favor of managed authentication.

addresses: CWE-798

External identity providers eliminate the need for hard-coded credentials in applications.

Mitigating Controls (NIST CSF 2.0)

Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→CSF cross-walk — links open the control.

PR.PS-06 mostly match
blocks

Secure SDLC practices directly prohibit embedding credentials in source code or binaries.

PR.AA-01 partial match
blocks

PR.AA-01's credential/key-management processes can reduce the incentive to embed secrets but do not address or detect hard-coded values in source code, so the weakness remains fully possible.

Mitigating Controls (ISO/IEC 27001:2022 Annex A)

Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→ISO cross-walk — links open the control.

finds

A.8.29's SOURCE+RUNTIME reach finds hard-coded passwords well: SAST detects password string literals, code review catches them, and penetration testing extracts them from binaries; the same bounded remainder as the CWE-798 anchor applies -- credentials assembled at build time, baked into images as configuration, or shipped inside binary-only third-party components.

prevents

Training/awareness addresses hard-coded passwords as a known anti-pattern (the clause explicitly names password security as a baseline control topic), and a developer who has been educated will sometimes choose not to hard-code credentials, but the weakness is a code-level defect introduced during implementation where convenience pressures and time-to-market routinely override training, so the effect is a minority one.

blocks

Network segregation can prevent untrusted domains from reaching an inbound authentication interface that uses a hard-coded password, but it leaves the credential exploitable from permitted network paths and does not prevent reuse of outbound hard-coded passwords.

prevents

A.8.24's key management guidance (generation, storage, distribution through proper processes) prevents hard-coded cryptographic keys in first-party code, but the clause addresses cryptography, not authentication credentials, so the password variant of CWE-798 is untouched; third-party and COTS components with embedded credentials are also outside its reach.

prevents

A.8.28 explicitly prohibits hard-coded passwords in its 'During coding' guidance (item e), so a system under the clause sees fewer instances arise, but the clause mandates a practice rather than a mechanism and the prohibition depends on developer compliance, third-party components, and the rigour of implementation — the same ceiling the owner set for A.8.28 on CWE-502 and CWE-79.

finds

A.8.30's programme includes acceptance testing (item d) and contractual audit rights (item i), which can surface hard-coded passwords in delivered code, but these are a minority of instances — most are caught by the supplier's own development-time testing (A.8.29), which A.8.30 only requires contractually rather than performs itself.

References