CVE-2018-2475

Description

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.

8.5
CVSS
Severity: High
CVSS 3.0 •
CVSS 2.0 •
EPSS 1.00% Top 25%
Vendor Advisory sap.com Vendor Advisory sap.com
Affected: SAP project “Gardener”
Published at:
Updated at:

References

Frequently Asked Questions

What is the severity of CVE-2018-2475?
CVE-2018-2475 has been scored as a high severity vulnerability.
How to fix CVE-2018-2475?
To fix CVE-2018-2475, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2018-2475 being actively exploited in the wild?
It is possible that CVE-2018-2475 is being exploited or will be exploited in a near future based on public information. According to its EPSS score, there is a ~1% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2018-2475?
CVE-2018-2475 affects SAP project “Gardener”.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.