{"answers":{"affected":"2 open source packages ship an affected version, including org.jenkins-ci.plugins:opsgenie. It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-34803 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-34803 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-34803 is a medium-severity vulnerability in Jenkins OpsGenie 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-34803 and fix it if it is affected.\n\nWhat it is: CVE-2022-34803 is a medium-severity vulnerability in Jenkins OpsGenie 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-34803 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.jenkins-ci.plugins:opsgenie (Maven): affected all versions up to 1.9; no fix listed\n- org.jenkins-ci.plugins:opsgenie (Maven): affected all versions up to 1.9; 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-34803/ (Markdown: https://insights.sbomify.com/CVE-2022-34803/index.md)","id":"CVE-2022-34803","markdown":"https://insights.sbomify.com/CVE-2022-34803/index.md","name":"CVE-2022-34803","record":{"aliases":["GHSA-273c-fjw8-v2w8"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Jenkins OpsGenie Plugin","requires_auth":"low_privilege","summary":"Attackers with Extended Read permission or file system access can view unencrypted OpsGenie API keys stored in Jenkins configuration files.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"jenkins","cpe":[{"product":"opsgenie","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-522","name":"Insufficiently Protected Credentials"}],"description":"Jenkins OpsGenie Plugin 1.9 and earlier stores API keys unencrypted in its global configuration file and in job config.xml files on the Jenkins controller where they can be viewed by users with Extended Read permission (config.xml), or access to 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":false,"headline":"Jenkins OpsGenie Plugin Plaintext Storage of a Password vulnerability","id":"CVE-2022-34803","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":"Jenkins OpsGenie Plugin vulnerable to Cleartext Transmission of Sensitive Information","id":"CVE-2022-34804"},"packages":[{"ecosystem":"Maven","fixed":[],"introduced":["0"],"last_affected":["1.9"],"package":"org.jenkins-ci.plugins:opsgenie","purl":null,"source":"GHSA-273c-fjw8-v2w8"},{"ecosystem":"Maven","fixed":[],"introduced":["0"],"last_affected":["1.9"],"package":"org.jenkins-ci.plugins:opsgenie","purl":"pkg:maven/org.jenkins-ci.plugins/opsgenie","source":"GHSA-273c-fjw8-v2w8"}],"prev":{"headline":"Plaintext Storage of a Password in Jenkins RocketChat Notifier Plugin","id":"CVE-2022-34802"},"products":["Jenkins OpsGenie Plugin"],"published":"2022-06-30","related":[{"cvss_score":4.3,"headline":"Jenkins OpsGenie Plugin vulnerable to Cleartext Transmission of Sensitive Information","id":"CVE-2022-34804","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 Extended Read permission or file system access can view unencrypted OpsGenie API keys stored in Jenkins configuration files.","url":"https://insights.sbomify.com/CVE-2022-34803/"}