{"answers":{"affected":"2 open source packages ship an affected version, including org.jenkins-ci.plugins:google-kubernetes-engine. It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-10365 in the wild and no public exploit code.","fix":"Upgrade org.jenkins-ci.plugins:google-kubernetes-engine to 0.6.3 or later.","what":"CVE-2019-10365 is a medium-severity vulnerability in Jenkins Google Kubernetes Engine Plugin, published on 31 Jul 2019. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-10365 and fix it if it is affected.\n\nWhat it is: CVE-2019-10365 is a medium-severity vulnerability in Jenkins Google Kubernetes Engine Plugin, published on 31 Jul 2019. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2019-10365 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.jenkins-ci.plugins:google-kubernetes-engine (Maven): affected all versions; fixed in 0.6.3\n- org.jenkins-ci.plugins:google-kubernetes-engine (Maven): affected all versions; fixed in 0.6.3\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-2019-10365/ (Markdown: https://insights.sbomify.com/CVE-2019-10365/index.md)","id":"CVE-2019-10365","markdown":"https://insights.sbomify.com/CVE-2019-10365/index.md","name":"CVE-2019-10365","record":{"aliases":["GHSA-xw4c-9434-3f7p"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Jenkins GKE Plugin","requires_auth":"low_privilege","summary":"Attackers with Job/Read permissions can access temporary access tokens stored in the project workspace, potentially leading to unauthorized access.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"jenkins","cpe":[{"product":"kubernetes_engine","vendor":"google"}],"cvss":{"score":4.3,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-668","name":"Exposure of Resource to Wrong Sphere"}],"description":"Jenkins Google Kubernetes Engine Plugin 0.6.2 and earlier created a temporary file containing a temporary access token in the project workspace, where it could be accessed by users with Job/Read permission.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Jenkins Google Kubernetes Engine Plugin vulnerable to Exposure of Resource to Wrong Sphere","id":"CVE-2019-10365","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"information_disclosure","year":"2019"},"n_packages":2,"n_references":2,"next":{"headline":"Skytap Cloud CI Plugin stored credentials in plain text","id":"CVE-2019-10366"},"packages":[{"ecosystem":"Maven","fixed":["0.6.3"],"introduced":["0"],"last_affected":[],"package":"org.jenkins-ci.plugins:google-kubernetes-engine","purl":null,"source":"GHSA-xw4c-9434-3f7p"},{"ecosystem":"Maven","fixed":["0.6.3"],"introduced":["0"],"last_affected":[],"package":"org.jenkins-ci.plugins:google-kubernetes-engine","purl":"pkg:maven/org.jenkins-ci.plugins/google-kubernetes-engine","source":"GHSA-xw4c-9434-3f7p"}],"prev":{"headline":"Jenkins Amazon EC2 Plugin leaked beginning of private key in system log","id":"CVE-2019-10364"},"products":["Jenkins Google Kubernetes Engine Plugin"],"published":"2019-07-31","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"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-08-04","vendors":["Jenkins project"]},"summary":"Attackers with Job/Read permissions can access temporary access tokens stored in the project workspace, potentially leading to unauthorized access.","url":"https://insights.sbomify.com/CVE-2019-10365/"}