{"answers":{"affected":"2 open source packages ship an affected version, including org.jenkins-ci.plugins:fortify. It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-2107 in the wild and no public exploit code.","fix":"Upgrade org.jenkins-ci.plugins:fortify to 19.2.30 or later.","what":"CVE-2020-2107 is a medium-severity vulnerability in Jenkins Fortify Plugin, published on 29 Jan 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-2107 and fix it if it is affected.\n\nWhat it is: CVE-2020-2107 is a medium-severity vulnerability in Jenkins Fortify Plugin, published on 29 Jan 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-2107 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.jenkins-ci.plugins:fortify (Maven): affected all versions; fixed in 19.2.30\n- org.jenkins-ci.plugins:fortify (Maven): affected all versions; fixed in 19.2.30\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-2107/ (Markdown: https://insights.sbomify.com/CVE-2020-2107/index.md)","id":"CVE-2020-2107","markdown":"https://insights.sbomify.com/CVE-2020-2107/index.md","name":"CVE-2020-2107","record":{"aliases":["GHSA-xr37-pjfh-qwwc"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Jenkins Fortify Plugin","requires_auth":"low_privilege","summary":"Attackers with Extended Read permission or master file system access can view unencrypted proxy server passwords stored in Jenkins job configuration files.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"jenkins","cpe":[{"product":"fortify","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 Fortify Plugin 19.1.29 and earlier stores proxy server passwords unencrypted in job config.xml files on the Jenkins master where they can be viewed by users with Extended Read permission, or 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":true,"headline":"Fortify Plugin stored credentials in plain text","id":"CVE-2020-2107","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":"XXE vulnerability in Jenkins WebSphere Deployer Plugin","id":"CVE-2020-2108"},"packages":[{"ecosystem":"Maven","fixed":["19.2.30"],"introduced":["0"],"last_affected":[],"package":"org.jenkins-ci.plugins:fortify","purl":null,"source":"GHSA-xr37-pjfh-qwwc"},{"ecosystem":"Maven","fixed":["19.2.30"],"introduced":["0"],"last_affected":[],"package":"org.jenkins-ci.plugins:fortify","purl":"pkg:maven/org.jenkins-ci.plugins/fortify","source":"GHSA-xr37-pjfh-qwwc"}],"prev":{"headline":"Stored XSS vulnerability in Code Coverage API Plugin","id":"CVE-2020-2106"},"products":["Jenkins Fortify Plugin"],"published":"2020-01-29","related":[{"cvss_score":4.3,"headline":"HTML injection vulnerability in Fortify Plugin","id":"CVE-2023-4303","kev_date_added":null,"published":"2023-08-21"},{"cvss_score":4.3,"headline":"Path traversal vulnerability in Jenkins Fortify Plugin","id":"CVE-2022-25188","kev_date_added":null,"published":"2022-02-15"},{"cvss_score":4.2,"headline":"CSRF vulnerability in Fortify Plugin allow capturing credentials","id":"CVE-2023-4301","kev_date_added":null,"published":"2023-08-21"},{"cvss_score":4.2,"headline":"Missing permission checks in Fortify Plugin allow capturing credentials","id":"CVE-2023-4302","kev_date_added":null,"published":"2023-08-21"}],"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 Extended Read permission or master file system access can view unencrypted proxy server passwords stored in Jenkins job configuration files.","url":"https://insights.sbomify.com/CVE-2020-2107/"}