{"answers":{"affected":"2 open source packages ship an affected version, including org.jenkins-ci.plugins:rpmsign-plugin. It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-36893 in the wild and no public exploit code.","fix":"Upgrade org.jenkins-ci.plugins:rpmsign-plugin to 0.5.1 or later.","what":"CVE-2022-36893 is a medium-severity missing authorization vulnerability in Jenkins rpmsign-plugin Plugin, published on 27 Jul 2022. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-36893 and fix it if it is affected.\n\nWhat it is: CVE-2022-36893 is a medium-severity missing authorization vulnerability in Jenkins rpmsign-plugin Plugin, published on 27 Jul 2022. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-36893 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.jenkins-ci.plugins:rpmsign-plugin (Maven): affected all versions; fixed in 0.5.1\n- org.jenkins-ci.plugins:rpmsign-plugin (Maven): affected all versions; fixed in 0.5.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-36893/ (Markdown: https://insights.sbomify.com/CVE-2022-36893/index.md)","id":"CVE-2022-36893","markdown":"https://insights.sbomify.com/CVE-2022-36893/index.md","name":"CVE-2022-36893","record":{"aliases":["GHSA-pw4g-jcp5-63m9"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Jenkins rpmsign plugin","requires_auth":"low_privilege","summary":"Attackers with read permissions can bypass authorization checks to inspect workspace file patterns in the Jenkins rpmsign plugin.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"jenkins","cpe":[{"product":"rpmsign-plugin","vendor":"jenkins"}],"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-862","name":"Missing Authorization"}],"description":"Jenkins rpmsign-plugin Plugin 0.5.0 and earlier does not perform a permission check in a method implementing form validation, allowing attackers with Item/Read permission but without Item/Workspace or Item/Configure permission to check whether attacker-specified file patterns match workspace 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":"Jenkins rpmsign-plugin does not perform a permission check in a method implementing form validation","id":"CVE-2022-36893","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"missing_authorization","year":"2022"},"n_packages":2,"n_references":2,"next":{"headline":"Arbitrary file write vulnerability in Jenkins CLIF Performance Testing plugin","id":"CVE-2022-36894"},"packages":[{"ecosystem":"Maven","fixed":["0.5.1"],"introduced":["0"],"last_affected":[],"package":"org.jenkins-ci.plugins:rpmsign-plugin","purl":null,"source":"GHSA-pw4g-jcp5-63m9"},{"ecosystem":"Maven","fixed":["0.5.1"],"introduced":["0"],"last_affected":[],"package":"org.jenkins-ci.plugins:rpmsign-plugin","purl":"pkg:maven/org.jenkins-ci.plugins/rpmsign-plugin","source":"GHSA-pw4g-jcp5-63m9"}],"prev":{"headline":"Jenkins rhnpush-plugin does not perform a permission check in a method implementing form validation","id":"CVE-2022-36892"},"products":["Jenkins rpmsign-plugin Plugin"],"published":"2022-07-27","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-03","vendors":["Jenkins project"]},"summary":"Attackers with read permissions can bypass authorization checks to inspect workspace file patterns in the Jenkins rpmsign plugin.","url":"https://insights.sbomify.com/CVE-2022-36893/"}