{"answers":{"affected":"2 open source packages ship an affected version, including org.jenkins-ci.plugins:pipeline-build-step. It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-2118 in the wild and no public exploit code.","fix":"Upgrade org.jenkins-ci.plugins:pipeline-build-step to 1.0.5 or later.","what":"CVE-2020-2118 is a medium-severity vulnerability in Jenkins Pipeline GitHub Notify Step Plugin, published on 12 Feb 2020. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-2118 and fix it if it is affected.\n\nWhat it is: CVE-2020-2118 is a medium-severity vulnerability in Jenkins Pipeline GitHub Notify Step Plugin, published on 12 Feb 2020. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2020-2118 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.jenkins-ci.plugins:pipeline-build-step (Maven): affected all versions; fixed in 1.0.5\n- org.jenkins-ci.plugins:pipeline-build-step (Maven): affected all versions; fixed in 1.0.5\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-2020-2118/ (Markdown: https://insights.sbomify.com/CVE-2020-2118/index.md)","id":"CVE-2020-2118","markdown":"https://insights.sbomify.com/CVE-2020-2118/index.md","name":"CVE-2020-2118","record":{"aliases":["GHSA-8p4m-62gp-33j4"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Jenkins plugin","requires_auth":"low_privilege","summary":"Attackers with read access can enumerate stored credential IDs due to missing permission checks in the Jenkins GitHub Notify Step Plugin.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"jenkins","cpe":[{"product":"pipeline_github_notify_step","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-276","name":"Incorrect Default Permissions"}],"description":"A missing permission check in Jenkins Pipeline GitHub Notify Step Plugin 1.0.4 and earlier in form-related methods allowed users with Overall/Read access to enumerate credentials ID 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":true,"headline":"Users with Overall/Read access can enumerate credential IDs in Pipeline GitHub Notify Step Plugin","id":"CVE-2020-2118","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"information_disclosure","year":"2020"},"n_packages":2,"n_references":2,"next":{"headline":"Client secret transmitted in plain text by Azure AD Plugin","id":"CVE-2020-2119"},"packages":[{"ecosystem":"Maven","fixed":["1.0.5"],"introduced":["0"],"last_affected":[],"package":"org.jenkins-ci.plugins:pipeline-build-step","purl":null,"source":"GHSA-8p4m-62gp-33j4"},{"ecosystem":"Maven","fixed":["1.0.5"],"introduced":["0"],"last_affected":[],"package":"org.jenkins-ci.plugins:pipeline-build-step","purl":"pkg:maven/org.jenkins-ci.plugins/pipeline-build-step","source":"GHSA-8p4m-62gp-33j4"}],"prev":{"headline":"Missing permission checks in Pipeline GitHub Notify Step Plugin allows capturing credentials","id":"CVE-2020-2117"},"products":["Jenkins Pipeline GitHub Notify Step Plugin"],"published":"2020-02-12","related":[{"cvss_score":8.8,"headline":"CSRF vulnerability in Pipeline GitHub Notify Step Plugin allows capturing credentials","id":"CVE-2020-2116","kev_date_added":null,"published":"2020-02-12"},{"cvss_score":4.3,"headline":"Missing permission checks in Pipeline GitHub Notify Step Plugin allows capturing credentials","id":"CVE-2020-2117","kev_date_added":null,"published":"2020-02-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":"2024-08-04","vendors":["Jenkins project"]},"summary":"Attackers with read access can enumerate stored credential IDs due to missing permission checks in the Jenkins GitHub Notify Step Plugin.","url":"https://insights.sbomify.com/CVE-2020-2118/"}