{"answers":{"affected":"2 open source packages ship an affected version, including RPD:bmc-rpd. It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-2127 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-2127 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-2127 is a medium-severity vulnerability in Jenkins BMC Release Package and Deployment 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-2127 and fix it if it is affected.\n\nWhat it is: CVE-2020-2127 is a medium-severity vulnerability in Jenkins BMC Release Package and Deployment 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-2127 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- RPD:bmc-rpd (Maven): affected all versions up to 1.1; no fix listed\n- RPD:bmc-rpd (Maven): affected all versions up to 1.1; 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-2020-2127/ (Markdown: https://insights.sbomify.com/CVE-2020-2127/index.md)","id":"CVE-2020-2127","markdown":"https://insights.sbomify.com/CVE-2020-2127/index.md","name":"CVE-2020-2127","record":{"aliases":["GHSA-2j3r-x6xc-qqqj"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Jenkins BMC plugin","requires_auth":"low_privilege","summary":"The Jenkins BMC Release Package and Deployment Plugin stores credentials unencrypted, allowing local file system access to expose sensitive information.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"jenkins","cpe":[{"product":"bmc_release_package_and_deployment","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 BMC Release Package and Deployment Plugin 1.1 and earlier stores credentials unencrypted in its global configuration file on the Jenkins master where they can be viewed by users with access to the master 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":"Credential stored in plain text by BMC Release Package and Deployment Plugin","id":"CVE-2020-2127","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"hardcoded_credentials","year":"2020"},"n_packages":2,"n_references":2,"next":{"headline":"Password stored in plain text by ECX Copy Data Management Plugin","id":"CVE-2020-2128"},"packages":[{"ecosystem":"Maven","fixed":[],"introduced":["0"],"last_affected":["1.1"],"package":"RPD:bmc-rpd","purl":null,"source":"GHSA-2j3r-x6xc-qqqj"},{"ecosystem":"Maven","fixed":[],"introduced":["0"],"last_affected":["1.1"],"package":"RPD:bmc-rpd","purl":"pkg:maven/RPD/bmc-rpd","source":"GHSA-2j3r-x6xc-qqqj"}],"prev":{"headline":"Token stored in plain text by DigitalOcean Plugin","id":"CVE-2020-2126"},"products":["Jenkins BMC Release Package and Deployment Plugin"],"published":"2020-02-12","related":[],"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":"The Jenkins BMC Release Package and Deployment Plugin stores credentials unencrypted, allowing local file system access to expose sensitive information.","url":"https://insights.sbomify.com/CVE-2020-2127/"}