{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-2475 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-2475 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-2475 is a high-severity missing authorization vulnerability in SAP project “Gardener”, published on 9 Oct 2018. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-2475 and fix it if it is affected.\n\nWhat it is: CVE-2018-2475 is a high-severity missing authorization vulnerability in SAP project “Gardener”, published on 9 Oct 2018. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2018-2475 in the wild and no public exploit code.\n\nAffected product: SAP project “Gardener”. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2018-2475/ (Markdown: https://insights.sbomify.com/CVE-2018-2475/index.md)","id":"CVE-2018-2475","markdown":"https://insights.sbomify.com/CVE-2018-2475/index.md","name":"CVE-2018-2475","record":{"aliases":["GHSA-g482-4r7c-68g6"],"analysis":{"component_type":"cloud_service","fix_type":"upgrade","impacts":["privilege_escalation","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Kubernetes management platform","requires_auth":"low_privilege","summary":"Missing network isolation allows a shoot cluster's API server to access private seed cluster services, potentially compromising other clusters.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"sap","cpe":[{"product":"gardener","vendor":"gardener"}],"cvss":{"score":8.5,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H","version":"3.0"},"cwes":[],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Missing authorization in project “Gardener”","id":"CVE-2018-2475","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2018"},"n_packages":0,"n_references":4,"next":{"headline":"Open redirect in SAP NetWeaver (forums)","id":"CVE-2018-2476"},"packages":[],"prev":{"headline":"Cross-site request forgery in SAP Fiori 1.0 for SAP ERP HCM (Approve Leave Request, version 2)","id":"CVE-2018-2474"},"products":["project “Gardener”"],"published":"2018-10-09","related":[{"cvss_score":9.9,"headline":"Bypassing project secret validation can lead to privilege escalation","id":"CVE-2025-47283","kev_date_added":null,"published":"2025-05-19"},{"cvss_score":9.9,"headline":"Gardener vulnerable to metadata injection for a project secret that can lead to privilege escalation","id":"CVE-2025-47284","kev_date_added":null,"published":"2025-05-19"},{"cvss_score":8.5,"headline":"Missing authorization in n/a","id":"CVE-2019-12494","kev_date_added":null,"published":"2019-06-05"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["SAP"]},"summary":"Missing network isolation allows a shoot cluster's API server to access private seed cluster services, potentially compromising other clusters.","url":"https://insights.sbomify.com/CVE-2018-2475/"}