{"answers":{"affected":"2 open source packages ship an affected version, including org.jenkins-ci.plugins:backlog. It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-2153 in the wild and no public exploit code.","fix":"Upgrade org.jenkins-ci.plugins:backlog to 2.5 or later.","what":"CVE-2020-2153 is a medium-severity vulnerability in Jenkins Backlog Plugin, published on 9 Mar 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-2153 and fix it if it is affected.\n\nWhat it is: CVE-2020-2153 is a medium-severity vulnerability in Jenkins Backlog Plugin, published on 9 Mar 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-2153 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.jenkins-ci.plugins:backlog (Maven): affected all versions; fixed in 2.5\n- org.jenkins-ci.plugins:backlog (Maven): affected all versions; fixed in 2.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-2153/ (Markdown: https://insights.sbomify.com/CVE-2020-2153/index.md)","id":"CVE-2020-2153","markdown":"https://insights.sbomify.com/CVE-2020-2153/index.md","name":"CVE-2020-2153","record":{"aliases":["GHSA-p68c-xg89-2g5r"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Jenkins Backlog Plugin","requires_auth":"low_privilege","summary":"Attackers can view Jenkins Backlog Plugin credentials in plain text via job configuration forms, leading to potential credential exposure.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"jenkins","cpe":[{"product":"backlog","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-319","name":"Cleartext Transmission of Sensitive Information"}],"description":"Jenkins Backlog Plugin 2.4 and earlier transmits configured credentials in plain text as part of job configuration forms, potentially resulting in their exposure.","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":"Credentials transmitted in plain text by Backlog Plugin","id":"CVE-2020-2153","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":"Jenkins Zephyr for JIRA Test Management Plugin stores credentials in plain text","id":"CVE-2020-2154"},"packages":[{"ecosystem":"Maven","fixed":["2.5"],"introduced":["0"],"last_affected":[],"package":"org.jenkins-ci.plugins:backlog","purl":null,"source":"GHSA-p68c-xg89-2g5r"},{"ecosystem":"Maven","fixed":["2.5"],"introduced":["0"],"last_affected":[],"package":"org.jenkins-ci.plugins:backlog","purl":"pkg:maven/org.jenkins-ci.plugins/backlog","source":"GHSA-p68c-xg89-2g5r"}],"prev":{"headline":"Jenkins Subversion Release Manager Plugin vulnerable to cross-site scripting (XSS)","id":"CVE-2020-2152"},"products":["Jenkins Backlog Plugin"],"published":"2020-03-09","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":"Attackers can view Jenkins Backlog Plugin credentials in plain text via job configuration forms, leading to potential credential exposure.","url":"https://insights.sbomify.com/CVE-2020-2153/"}