{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-1002100 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-1002100 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-1002100 is a medium-severity vulnerability in Kubernetes Kubernetes, published on 14 Sep 2017. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2017-1002100 and fix it if it is affected.\n\nWhat it is: CVE-2017-1002100 is a medium-severity vulnerability in Kubernetes Kubernetes, published on 14 Sep 2017. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2017-1002100 in the wild and no public exploit code.\n\nAffected product: Kubernetes Kubernetes. 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-2017-1002100/ (Markdown: https://insights.sbomify.com/CVE-2017-1002100/index.md)","id":"CVE-2017-1002100","markdown":"https://insights.sbomify.com/CVE-2017-1002100/index.md","name":"CVE-2017-1002100","record":{"aliases":["GHSA-rj88-p797-v9xw"],"analysis":{"component_type":"cloud_service","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Kubernetes Azure provider","requires_auth":"low_privilege","summary":"Attackers with cluster or Azure portal access can read data from Persistent Volumes due to insecure default permissions exposing URIs.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"kubernetes","cpe":[{"product":"kubernetes","vendor":"kubernetes"}],"cvss":{"score":6.5,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"Default access permissions for Persistent Volumes (PVs) created by the Kubernetes Azure cloud provider in versions 1.6.0 to 1.6.5 are set to \"container\" which exposes a URI that can be accessed without authentication on the public internet. Access to the URI string requires privileged access to the Kubernetes cluster or authenticated access to the Azure portal.","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":"Information disclosure in Kubernetes","id":"CVE-2017-1002100","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"kubernetes:kubernetes","products":["kubernetes:kubernetes"],"type":"information_disclosure","year":"2017"},"n_packages":0,"n_references":2,"next":{"headline":"Path traversal in Kubernetes","id":"CVE-2017-1002101"},"packages":[],"prev":{"headline":"SQL injection in wordpress-gallery-transformation","id":"CVE-2017-1002028"},"products":["Kubernetes"],"published":"2017-09-14","related":[{"cvss_score":9.8,"headline":"Privilege Escalation in Kubernetes","id":"CVE-2018-1002105","kev_date_added":null,"published":"2018-12-05"},{"cvss_score":9.8,"headline":"Kubernetes Privilege Escalation","id":"CVE-2017-1000056","kev_date_added":null,"published":"2017-07-13"},{"cvss_score":9.8,"headline":"Authorization bypass in Openshift","id":"CVE-2016-1906","kev_date_added":null,"published":"2016-02-03"},{"cvss_score":8.8,"headline":"Kubernetes - Windows nodes - Insufficient input sanitization leads to privilege escalation","id":"CVE-2023-3676","kev_date_added":null,"published":"2023-10-31"},{"cvss_score":8.8,"headline":"Kubernetes - Windows nodes - Insufficient input sanitization leads to privilege escalation","id":"CVE-2023-3955","kev_date_added":null,"published":"2023-10-31"},{"cvss_score":8.8,"headline":"Symlink Exchange Can Allow Host Filesystem Access","id":"CVE-2021-25741","kev_date_added":null,"published":"2021-09-20"},{"cvss_score":8.8,"headline":"Path traversal in Kubernetes","id":"CVE-2017-1002101","kev_date_added":null,"published":"2018-03-13"}],"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":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-09-16","vendors":["Kubernetes"]},"summary":"Attackers with cluster or Azure portal access can read data from Persistent Volumes due to insecure default permissions exposing URIs.","url":"https://insights.sbomify.com/CVE-2017-1002100/"}