dbcve.org
GardenerApplication

CVE-2018-2475

HIGH · 8.5 CVSS v3.0 Published 2018-10-09
Fix available
A fix is available. Upgrade to 0.12.4 or later.
See remediation →
91/100
Remediation priority · Urgent
Remotely reachable 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
Following the Gardener architecture, the Kubernetes apiserver of a Gardener managed shoot cluster resides in the corresponding seed cluster. Due to missing network isolation a shoot's apiserver can access services/endpoints in the private network of its corresponding seed cluster. Combined with other minor Kubernetes security issues, the missing network isolation theoretically can lead to compromise other shoot or seed clusters in the "Gardener" context. The issue is rated high due to the high impact of a potential exploitation in "Gardener" context. This was fixed in Gardener release 0.12.4.

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 · high confidence

In Gardener's architecture, the Kubernetes apiserver for managed shoot clusters resides in seed clusters. Due to missing network isolation, a shoot's apiserver can access services and endpoints in its corresponding seed cluster's private network. Combined with other minor Kubernetes security issues, this can theoretically allow compromise of other shoot or seed clusters.

MitigationImplement network isolation policies between shoot cluster apiservers and seed cluster private networks to restrict unauthorized access. Upgrade to Gardener release 0.12.4 or later.

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
GardenerApplication
Affected:< 0.12.4

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
High
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:C/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. Identify Gardener version
    Query the Gardener API server for its version using 'kubectl get pods -n garden' and check image tags or query the Gardener API for version information
    Affected if The installed Gardener version is lower than 0.12.4
  2. Verify shoot apiserver deployment location
    Confirm that the shoot cluster's Kubernetes apiserver runs in the seed cluster by checking the seed cluster for shoot API server pods: 'kubectl get pods -n <seed-namespace> | grep apiserver'
    Affected if Shoot API server pods are running in the seed cluster (this is the vulnerable architecture)
  3. Check for network policies between shoot and seed
    Inspect NetworkPolicy resources in the seed cluster namespace where shoot API server runs: 'kubectl get networkpolicies -n <seed-namespace>'
    Affected if No NetworkPolicy exists to restrict the shoot apiserver's access to the seed's private network, or policies do not block access to seed cluster services
  4. Test network reachability from shoot apiserver
    From a shoot cluster context, attempt to reach seed cluster internal services using the seed's internal DNS or service endpoints (e.g., 'kubectl exec -it <test-pod> -- curl http://<seed-service>.<seed-namespace>.svc.cluster.local')
    Affected if The shoot apiserver can successfully reach services in the seed cluster's private network, indicating missing isolation

A user is affected if running Gardener version lower than 0.12.4 with shoot apiservers deployed in seed clusters and no network isolation policies blocking shoot-to-seed private network communication.

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
Upgrade available Upgrade to 0.12.4 or later
Fixed in 0.12.4
Interim mitigation

Implement network isolation policies between shoot cluster apiservers and seed cluster private networks to restrict unauthorized access. Upgrade to Gardener release 0.12.4 or later.

Fix this in Gardener Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-2475 — 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-2018-2475 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