{"answers":{"affected":"2 open source packages ship an affected version, including org.jenkins-ci.plugins:threadfix. It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-34209 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-34209 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-34209 is a medium-severity vulnerability in Jenkins ThreadFix Plugin, published on 22 Jun 2022. 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-2022-34209 and fix it if it is affected.\n\nWhat it is: CVE-2022-34209 is a medium-severity vulnerability in Jenkins ThreadFix Plugin, published on 22 Jun 2022. 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-2022-34209 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.jenkins-ci.plugins:threadfix (Maven): affected all versions up to 1.5.4; no fix listed\n- org.jenkins-ci.plugins:threadfix (Maven): affected all versions up to 1.5.4; no fix listed\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-2022-34209/ (Markdown: https://insights.sbomify.com/CVE-2022-34209/index.md)","id":"CVE-2022-34209","markdown":"https://insights.sbomify.com/CVE-2022-34209/index.md","name":"CVE-2022-34209","record":{"aliases":["GHSA-rq99-93c5-33f6"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Jenkins ThreadFix Plugin","requires_auth":"none","summary":"Attackers can exploit CSRF to force Jenkins users to connect to malicious URLs via the ThreadFix Plugin.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"jenkins","cpe":[{"product":"threadfix","vendor":"jenkins"}],"cvss":{"score":6.5,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"A cross-site request forgery (CSRF) vulnerability in Jenkins ThreadFix Plugin 1.5.4 and earlier allows attackers to connect to an attacker-specified URL.","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":false,"headline":"Cross-Site Request Forgery in Jenkins ThreadFix Plugin","id":"CVE-2022-34209","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"csrf","year":"2022"},"n_packages":2,"n_references":1,"next":{"headline":"Missing permission check in Jenkins ThreadFix Plugin","id":"CVE-2022-34210"},"packages":[{"ecosystem":"Maven","fixed":[],"introduced":["0"],"last_affected":["1.5.4"],"package":"org.jenkins-ci.plugins:threadfix","purl":null,"source":"GHSA-rq99-93c5-33f6"},{"ecosystem":"Maven","fixed":[],"introduced":["0"],"last_affected":["1.5.4"],"package":"org.jenkins-ci.plugins:threadfix","purl":"pkg:maven/org.jenkins-ci.plugins/threadfix","source":"GHSA-rq99-93c5-33f6"}],"prev":{"headline":"Jenkins Beaker builder Plugin Missing Authorization vulnerability","id":"CVE-2022-34208"},"products":["Jenkins ThreadFix Plugin"],"published":"2022-06-22","related":[{"cvss_score":6.5,"headline":"Missing permission check in Jenkins ThreadFix Plugin","id":"CVE-2022-34210","kev_date_added":null,"published":"2022-06-22"}],"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-03","vendors":["Jenkins project"]},"summary":"Attackers can exploit CSRF to force Jenkins users to connect to malicious URLs via the ThreadFix Plugin.","url":"https://insights.sbomify.com/CVE-2022-34209/"}