{"answers":{"affected":"2 open source packages ship an affected version, including org.jenkins-ci.plugins:jira. It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-49653 in the wild and no public exploit code.","fix":"Upgrade org.jenkins-ci.plugins:jira to 3.12 or later.","what":"CVE-2023-49653 is a medium-severity vulnerability in Jenkins Jira Plugin, published on 29 Nov 2023. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-49653 and fix it if it is affected.\n\nWhat it is: CVE-2023-49653 is a medium-severity vulnerability in Jenkins Jira Plugin, published on 29 Nov 2023. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2023-49653 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.jenkins-ci.plugins:jira (Maven): affected all versions; fixed in 3.12\n- org.jenkins-ci.plugins:jira (Maven): affected all versions; fixed in 3.12\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-2023-49653/ (Markdown: https://insights.sbomify.com/CVE-2023-49653/index.md)","id":"CVE-2023-49653","markdown":"https://insights.sbomify.com/CVE-2023-49653/index.md","name":"CVE-2023-49653","record":{"aliases":["GHSA-qmhq-876f-cr65"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Jenkins Jira Plugin","requires_auth":"low_privilege","summary":"Attackers with Item/Configure permission can capture unauthorized credentials due to improper context handling in the Jenkins Jira Plugin.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"jenkins","cpe":[{"product":"jira","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-522","name":"Insufficiently Protected Credentials"}],"description":"Jenkins Jira Plugin 3.11 and earlier does not set the appropriate context for credentials lookup, allowing attackers with Item/Configure permission to access and capture credentials they are not entitled to.","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 Jira Plugin vulnerable to exposure of system-scoped credentials","id":"CVE-2023-49653","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"information_disclosure","year":"2023"},"n_packages":2,"n_references":2,"next":{"headline":"Jenkins MATLAB Plugin missing permission checks","id":"CVE-2023-49654"},"packages":[{"ecosystem":"Maven","fixed":["3.12"],"introduced":["0"],"last_affected":[],"package":"org.jenkins-ci.plugins:jira","purl":null,"source":"GHSA-qmhq-876f-cr65"},{"ecosystem":"Maven","fixed":["3.12"],"introduced":["0"],"last_affected":[],"package":"org.jenkins-ci.plugins:jira","purl":"pkg:maven/org.jenkins-ci.plugins/jira","source":"GHSA-qmhq-876f-cr65"}],"prev":{"headline":"Jenkins Google Compute Engine Plugin has incorrect permission checks","id":"CVE-2023-49652"},"products":["Jenkins Jira Plugin"],"published":"2023-11-29","related":[{"cvss_score":9.9,"headline":"Jenkins JIRA Plugin allows users to select and use credentials with System scope","id":"CVE-2019-16541","kev_date_added":null,"published":"2019-11-21"},{"cvss_score":8.8,"headline":"Jenkins Jira Plugin Incorrect Authorization vulnerability","id":"CVE-2018-1000412","kev_date_added":null,"published":"2019-01-09"},{"cvss_score":5.4,"headline":"Stored Cross-site Scripting vulnerability in Jenkins Jira Plugin","id":"CVE-2022-29041","kev_date_added":null,"published":"2022-04-12"}],"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":"2025-02-13","vendors":["Jenkins Project"]},"summary":"Attackers with Item/Configure permission can capture unauthorized credentials due to improper context handling in the Jenkins Jira Plugin.","url":"https://insights.sbomify.com/CVE-2023-49653/"}