{"answers":{"affected":"2 open source packages ship an affected version, including io.jenkins.docker:docker-plugin. It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-10340 in the wild and no public exploit code.","fix":"Upgrade io.jenkins.docker:docker-plugin to 1.1.7 or later.","what":"CVE-2019-10340 is a high-severity vulnerability in Jenkins Docker Plugin, published on 11 Jul 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2019-10340 and fix it if it is affected.\n\nWhat it is: CVE-2019-10340 is a high-severity vulnerability in Jenkins Docker Plugin, published on 11 Jul 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2019-10340 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- io.jenkins.docker:docker-plugin (Maven): affected all versions; fixed in 1.1.7\n- io.jenkins.docker:docker-plugin (Maven): affected all versions; fixed in 1.1.7\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-10340/ (Markdown: https://insights.sbomify.com/CVE-2019-10340/index.md)","id":"CVE-2019-10340","markdown":"https://insights.sbomify.com/CVE-2019-10340/index.md","name":"CVE-2019-10340","record":{"aliases":["GHSA-m6gf-p26p-mx2w"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Jenkins Docker Plugin","requires_auth":"none","summary":"Attackers can trick users with read access into connecting to malicious URLs, potentially capturing stored Jenkins credentials.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"jenkins","cpe":[{"product":"docker","vendor":"jenkins"}],"cvss":{"score":8.8,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"A cross-site request forgery vulnerability in Jenkins Docker Plugin 1.1.6 and earlier in DockerAPI.DescriptorImpl#doTestConnection allowed users with Overall/Read access to connect to an attacker-specified URL using attacker-specified credentials IDs obtained through another method, capturing credentials stored in Jenkins.","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 Docker Plugin contains Cross-Site Request Forgery","id":"CVE-2019-10340","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"csrf","year":"2019"},"n_packages":2,"n_references":3,"next":{"headline":"Missing permission check in Jenkins Docker Plugin","id":"CVE-2019-10341"},"packages":[{"ecosystem":"Maven","fixed":["1.1.7"],"introduced":["0"],"last_affected":[],"package":"io.jenkins.docker:docker-plugin","purl":null,"source":"GHSA-m6gf-p26p-mx2w"},{"ecosystem":"Maven","fixed":["1.1.7"],"introduced":["0"],"last_affected":[],"package":"io.jenkins.docker:docker-plugin","purl":"pkg:maven/io.jenkins.docker/docker-plugin","source":"GHSA-m6gf-p26p-mx2w"}],"prev":{"headline":"Jenkins JX Resources Plugin missing permission check","id":"CVE-2019-10339"},"products":["Jenkins Docker Plugin"],"published":"2019-07-11","related":[{"cvss_score":6.5,"headline":"Missing permission check in Jenkins Docker Plugin","id":"CVE-2019-10341","kev_date_added":null,"published":"2019-07-11"},{"cvss_score":4.3,"headline":"Missing permission check in Jenkins Docker Plugin","id":"CVE-2019-10342","kev_date_added":null,"published":"2019-07-11"}],"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 can trick users with read access into connecting to malicious URLs, potentially capturing stored Jenkins credentials.","url":"https://insights.sbomify.com/CVE-2019-10340/"}