{"answers":{"affected":"2 open source packages ship an affected version, including org.jenkins-ci.plugins:embeddable-build-status. It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-34179 in the wild and no public exploit code.","fix":"Upgrade org.jenkins-ci.plugins:embeddable-build-status to 2.0.4 or later.","what":"CVE-2022-34179 is a high-severity path traversal vulnerability in Jenkins Embeddable Build Status Plugin, published on 22 Jun 2022. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-34179 and fix it if it is affected.\n\nWhat it is: CVE-2022-34179 is a high-severity path traversal vulnerability in Jenkins Embeddable Build Status Plugin, published on 22 Jun 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-34179 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.jenkins-ci.plugins:embeddable-build-status (Maven): affected all versions; fixed in 2.0.4\n- org.jenkins-ci.plugins:embeddable-build-status (Maven): affected all versions; fixed in 2.0.4\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-34179/ (Markdown: https://insights.sbomify.com/CVE-2022-34179/index.md)","id":"CVE-2022-34179","markdown":"https://insights.sbomify.com/CVE-2022-34179/index.md","name":"CVE-2022-34179","record":{"aliases":["GHSA-93mx-2vf9-28c4"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Jenkins build status plugin","requires_auth":"none","summary":"Attackers can read arbitrary SVG files from the Jenkins controller file system via a path traversal flaw in the Embeddable Build Status Plugin.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"jenkins","cpe":[{"product":"embeddable_build_status","vendor":"jenkins"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"Jenkins Embeddable Build Status Plugin 2.0.3 and earlier allows specifying a `style` query parameter that is used to choose a different SVG image style without restricting possible values, resulting in a relative path traversal vulnerability that allows attackers without Overall/Read permission to specify paths to other SVG images on the Jenkins controller file system.","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":"Path Traversal vulnerability in Jenkins Embeddable Build Status Plugin","id":"CVE-2022-34179","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"path_traversal","year":"2022"},"n_packages":2,"n_references":1,"next":{"headline":"Improper authorization in Jenkins Embeddable Build Status Plugin bypasses ViewStatus permission requirement","id":"CVE-2022-34180"},"packages":[{"ecosystem":"Maven","fixed":["2.0.4"],"introduced":["0"],"last_affected":[],"package":"org.jenkins-ci.plugins:embeddable-build-status","purl":null,"source":"GHSA-93mx-2vf9-28c4"},{"ecosystem":"Maven","fixed":["2.0.4"],"introduced":["0"],"last_affected":[],"package":"org.jenkins-ci.plugins:embeddable-build-status","purl":"pkg:maven/org.jenkins-ci.plugins/embeddable-build-status","source":"GHSA-93mx-2vf9-28c4"}],"prev":{"headline":"Reflected Cross site scripting in Jenkins Embeddable Build Status Plugin","id":"CVE-2022-34178"},"products":["Jenkins Embeddable Build Status Plugin"],"published":"2022-06-22","related":[{"cvss_score":7.5,"headline":"Improper authorization in Jenkins Embeddable Build Status Plugin bypasses ViewStatus permission requirement","id":"CVE-2022-34180","kev_date_added":null,"published":"2022-06-22"},{"cvss_score":6.1,"headline":"Reflected Cross site scripting in Jenkins Embeddable Build Status Plugin","id":"CVE-2022-34178","kev_date_added":null,"published":"2022-06-22"},{"cvss_score":6.1,"headline":"Jenkins Embeddable Build Status Plugin contains Cross-site Scripting","id":"CVE-2019-10346","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-03","vendors":["Jenkins project"]},"summary":"Attackers can read arbitrary SVG files from the Jenkins controller file system via a path traversal flaw in the Embeddable Build Status Plugin.","url":"https://insights.sbomify.com/CVE-2022-34179/"}