Project “Gardener”
Approved changes feed: RSS · Atom
cpe:2.3:a:sap:project_“gardener”:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Sap (dd5aa0c0-20b0-5c86-a937-aa29f1a33b77) |
|---|---|
| Product | Project “Gardener” (bbbefdcb-1d51-5e75-8dbc-9a67511ea07a) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2018-2475 |
vulnerable | 2026-06-08 05:11:37.224829 |
Details available
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.
Published: 2018-10-09T13:00:00.000Z
Updated: 2024-08-05T04:21:33.648Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.