{"answers":{"affected":"2 open source packages ship an affected version, including org.jenkins-ci.plugins:mercurial. It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-30948 in the wild and no public exploit code.","fix":"Upgrade org.jenkins-ci.plugins:mercurial to 2.16.1 or later.","what":"CVE-2022-30948 is a high-severity path traversal vulnerability in Jenkins Mercurial Plugin, published on 17 May 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-30948 and fix it if it is affected.\n\nWhat it is: CVE-2022-30948 is a high-severity path traversal vulnerability in Jenkins Mercurial Plugin, published on 17 May 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-30948 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.jenkins-ci.plugins:mercurial (Maven): affected all versions; fixed in 2.16.1\n- org.jenkins-ci.plugins:mercurial (Maven): affected all versions; fixed in 2.16.1\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-30948/ (Markdown: https://insights.sbomify.com/CVE-2022-30948/index.md)","id":"CVE-2022-30948","markdown":"https://insights.sbomify.com/CVE-2022-30948/index.md","name":"CVE-2022-30948","record":{"aliases":["GHSA-5786-3qjg-mr88"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Jenkins Mercurial Plugin","requires_auth":"none","summary":"Attackers with pipeline configuration access can use local paths to read SCM contents from other projects on the Jenkins controller.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"jenkins","cpe":[{"product":"mercurial","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":[],"description":"Jenkins Mercurial Plugin 2.16 and earlier allows attackers able to configure pipelines to check out some SCM repositories stored on the Jenkins controller's file system using local paths as SCM URLs, obtaining limited information about other projects' SCM contents.","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 in Jenkins Mercurial Plugin","id":"CVE-2022-30948","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"path_traversal","year":"2022"},"n_packages":2,"n_references":2,"next":{"headline":"Path traversal in Jenkins REPO Plugin","id":"CVE-2022-30949"},"packages":[{"ecosystem":"Maven","fixed":["2.16.1"],"introduced":["0"],"last_affected":[],"package":"org.jenkins-ci.plugins:mercurial","purl":null,"source":"GHSA-5786-3qjg-mr88"},{"ecosystem":"Maven","fixed":["2.16.1"],"introduced":["0"],"last_affected":[],"package":"org.jenkins-ci.plugins:mercurial","purl":"pkg:maven/org.jenkins-ci.plugins/mercurial","source":"GHSA-5786-3qjg-mr88"}],"prev":{"headline":"Path traversal in Jenkins Git Mercurial and Repo Plugins","id":"CVE-2022-30947"},"products":["Jenkins Mercurial Plugin"],"published":"2022-05-17","related":[{"cvss_score":6.5,"headline":"XXE vulnerability in Jenkins Mercurial Plugin","id":"CVE-2020-2305","kev_date_added":null,"published":"2020-11-04"},{"cvss_score":5.3,"headline":"Webhook endpoint discloses job names to unauthorized users in Jenkins Mercurial Plugin","id":"CVE-2022-43410","kev_date_added":null,"published":"2022-10-19"},{"cvss_score":5.3,"headline":"Incorrect Authorization in Jenkins Mercurial Plugin","id":"CVE-2018-1000112","kev_date_added":null,"published":"2018-03-13"},{"cvss_score":4.3,"headline":"Missing Authorization in Jenkins Mercurial Plugin","id":"CVE-2020-2306","kev_date_added":null,"published":"2020-11-04"}],"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":"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 with pipeline configuration access can use local paths to read SCM contents from other projects on the Jenkins controller.","url":"https://insights.sbomify.com/CVE-2022-30948/"}