{"answers":{"affected":"2 open source packages ship an affected version, including org.jenkins-ci.plugins:support-core. It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-25187 in the wild and no public exploit code.","fix":"Upgrade org.jenkins-ci.plugins:support-core to 2.79.1 or later.","what":"CVE-2022-25187 is a medium-severity vulnerability in Jenkins Support Core Plugin, published on 15 Feb 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-25187 and fix it if it is affected.\n\nWhat it is: CVE-2022-25187 is a medium-severity vulnerability in Jenkins Support Core Plugin, published on 15 Feb 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-25187 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.jenkins-ci.plugins:support-core (Maven): affected all versions; fixed in 2.79.1\n- org.jenkins-ci.plugins:support-core (Maven): affected all versions; fixed in 2.79.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-25187/ (Markdown: https://insights.sbomify.com/CVE-2022-25187/index.md)","id":"CVE-2022-25187","markdown":"https://insights.sbomify.com/CVE-2022-25187/index.md","name":"CVE-2022-25187","record":{"aliases":["GHSA-5m8f-v3gw-h94w"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Jenkins Support Plugin","requires_auth":"low_privilege","summary":"Attackers can access sensitive information in Jenkins support bundles due to insufficient redaction in the Support Core Plugin.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"jenkins","cpe":[{"product":"support_core","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-212","name":"Improper Removal of Sensitive Information Before Storage or Transfer"}],"description":"Jenkins Support Core Plugin 2.79 and earlier does not redact some sensitive information in the support bundle.","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 Support Core Plugin stores sensitive data in plain text","id":"CVE-2022-25187","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":"Path traversal vulnerability in Jenkins Fortify Plugin","id":"CVE-2022-25188"},"packages":[{"ecosystem":"Maven","fixed":["2.79.1"],"introduced":["0"],"last_affected":[],"package":"org.jenkins-ci.plugins:support-core","purl":null,"source":"GHSA-5m8f-v3gw-h94w"},{"ecosystem":"Maven","fixed":["2.79.1"],"introduced":["0"],"last_affected":[],"package":"org.jenkins-ci.plugins:support-core","purl":"pkg:maven/org.jenkins-ci.plugins/support-core","source":"GHSA-5m8f-v3gw-h94w"}],"prev":{"headline":"Agent-to-controller security bypass in Jenkins HashiCorp Vault Plugin","id":"CVE-2022-25186"},"products":["Jenkins Support Core Plugin"],"published":"2022-02-15","related":[{"cvss_score":6.5,"headline":"Incorrect permission checks in Jenkins Support Core Plugin","id":"CVE-2022-45383","kev_date_added":null,"published":"2022-11-15"},{"cvss_score":6.5,"headline":"Missing permission check in Jenkins Support Core Plugin","id":"CVE-2019-16539","kev_date_added":null,"published":"2019-11-21"},{"cvss_score":6.5,"headline":"Jenkins Support Core Plugin allowed users with Overall/Read permission to delete arbitrary files","id":"CVE-2019-16540","kev_date_added":null,"published":"2019-11-21"},{"cvss_score":5.3,"headline":"Support bundles can include user session IDs in Jenkins Support Core Plugin","id":"CVE-2021-21621","kev_date_added":null,"published":"2021-02-24"}],"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 can access sensitive information in Jenkins support bundles due to insufficient redaction in the Support Core Plugin.","url":"https://insights.sbomify.com/CVE-2022-25187/"}