{"answers":{"affected":"2 open source packages ship an affected version, including net.praqma:rqm-plugin. It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-34810 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-34810 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-34810 is a medium-severity vulnerability in Jenkins RQM Plugin, published on 30 Jun 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-34810 and fix it if it is affected.\n\nWhat it is: CVE-2022-34810 is a medium-severity vulnerability in Jenkins RQM Plugin, published on 30 Jun 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-34810 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- net.praqma:rqm-plugin (Maven): affected all versions up to 2.8; no fix listed\n- net.praqma:rqm-plugin (Maven): affected all versions up to 2.8; 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-34810/ (Markdown: https://insights.sbomify.com/CVE-2022-34810/index.md)","id":"CVE-2022-34810","markdown":"https://insights.sbomify.com/CVE-2022-34810/index.md","name":"CVE-2022-34810","record":{"aliases":["GHSA-2348-ccqj-8p27"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Jenkins RQM Plugin","requires_auth":"low_privilege","summary":"Attackers with read permissions can enumerate stored credential IDs in the Jenkins RQM Plugin due to a missing authorization check.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"jenkins","cpe":[{"product":"rqm","vendor":"jenkins"}],"cvss":{"score":6.5,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"}],"description":"A missing check in Jenkins RQM Plugin 2.8 and earlier allows attackers with Overall/Read permission to enumerate credentials IDs of 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":false,"headline":"Jenkins RQM Plugin allows enumerating credentials IDs due to missing permission check","id":"CVE-2022-34810","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"information_disclosure","year":"2022"},"n_packages":2,"n_references":1,"next":{"headline":"Missing Authorization in Jenkins XPath Configuration Viewer Plugin","id":"CVE-2022-34811"},"packages":[{"ecosystem":"Maven","fixed":[],"introduced":["0"],"last_affected":["2.8"],"package":"net.praqma:rqm-plugin","purl":null,"source":"GHSA-2348-ccqj-8p27"},{"ecosystem":"Maven","fixed":[],"introduced":["0"],"last_affected":["2.8"],"package":"net.praqma:rqm-plugin","purl":"pkg:maven/net.praqma/rqm-plugin","source":"GHSA-2348-ccqj-8p27"}],"prev":{"headline":"Password stored in plain text by Jenkins RQM Plugin","id":"CVE-2022-34809"},"products":["Jenkins RQM Plugin"],"published":"2022-06-30","related":[{"cvss_score":9.8,"headline":"Jenkins RQM Plugin vulnerable to Improper Restriction of XML External Entity Reference","id":"CVE-2022-41241","kev_date_added":null,"published":"2022-09-21"},{"cvss_score":6.5,"headline":"Password stored in plain text by Jenkins RQM Plugin","id":"CVE-2022-34809","kev_date_added":null,"published":"2022-06-30"}],"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 enumerate stored credential IDs in the Jenkins RQM Plugin due to a missing authorization check.","url":"https://insights.sbomify.com/CVE-2022-34810/"}