dbcve.org
MinikubeApplication · Kubernetes

CVE-2023-1174

CRITICAL · 9.8 CVSS v3.1 Published 2023-05-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
This vulnerability exposes a network port in minikube running on macOS with Docker driver that could enable unexpected remote access to the minikube container.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

This CVE exposes a network port in minikube when running on macOS with the Docker driver, allowing unexpected remote access to the minikube container. The vulnerability stems from insecure network port exposure during minikube's container networking configuration on this specific platform and driver combination.

MitigationConfigure firewall rules to block unauthorized access to the exposed port, or modify minikube's network configuration to disable the unnecessary port exposure on macOS with Docker driver.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
MinikubeApplication
Affected:= 1.26.0= 1.26.1= 1.27.0= 1.27.1= 1.28.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check minikube version
    Run 'minikube version' to obtain the installed version number
    Affected if Version is 1.26.0, 1.26.1, 1.27.0, 1.27.1, or 1.28.0
  2. Verify operating system
    Run 'uname -s' or check system information to confirm macOS
    Affected if Operating system is macOS
  3. Check minikube driver
    Run 'minikube profile list' or 'minikube config view' to identify the active driver
    Affected if Driver is set to Docker
  4. Inspect active profile configuration
    Run 'minikube profile list' and examine the Driver field for the active profile
    Affected if Using Docker driver on macOS with an affected version
  5. Detect unexpected listening ports
    Run 'netstat -an | grep LISTEN' or 'lsof -i -P' on the host to identify ports bound to 0.0.0.0 that may be exposed by minikube
    Affected if Unexpected ports are listening and accessible from the network on macOS with Docker driver

User is affected if running minikube version 1.26.0-1.28.0 on macOS with the Docker driver and an unexpected network port is exposed and accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Configure firewall rules to block unauthorized access to the exposed port, or modify minikube's network configuration to disable the unnecessary port exposure on macOS with Docker driver.

Fix this in Minikube Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,620
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,592.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-1174 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-1174 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data