{"answers":{"affected":"2 open source packages ship an affected version, including org.jenkins-ci.plugins:logstash. It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-2143 in the wild and no public exploit code.","fix":"Upgrade org.jenkins-ci.plugins:logstash to 2.3.2 or later.","what":"CVE-2020-2143 is a medium-severity vulnerability in Jenkins Logstash Plugin, published on 9 Mar 2020. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-2143 and fix it if it is affected.\n\nWhat it is: CVE-2020-2143 is a medium-severity vulnerability in Jenkins Logstash Plugin, published on 9 Mar 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2020-2143 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.jenkins-ci.plugins:logstash (Maven): affected all versions; fixed in 2.3.2\n- org.jenkins-ci.plugins:logstash (Maven): affected all versions; fixed in 2.3.2\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-2143/ (Markdown: https://insights.sbomify.com/CVE-2020-2143/index.md)","id":"CVE-2020-2143","markdown":"https://insights.sbomify.com/CVE-2020-2143/index.md","name":"CVE-2020-2143","record":{"aliases":["GHSA-5pg8-f89x-wjcx"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Jenkins Logstash Plugin","requires_auth":"none","summary":"Attackers can view Logstash credentials in plain text via the Jenkins configuration form, exposing sensitive authentication data.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"jenkins","cpe":[{"product":"logstash","vendor":"jenkins"}],"cvss":{"score":5.3,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/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 Logstash Plugin 2.3.1 and earlier transmits configured credentials in plain text as part of its global Jenkins configuration form, 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 Jenkins Logstash Plugin","id":"CVE-2020-2143","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 Rundeck Plugin","id":"CVE-2020-2144"},"packages":[{"ecosystem":"Maven","fixed":["2.3.2"],"introduced":["0"],"last_affected":[],"package":"org.jenkins-ci.plugins:logstash","purl":null,"source":"GHSA-5pg8-f89x-wjcx"},{"ecosystem":"Maven","fixed":["2.3.2"],"introduced":["0"],"last_affected":[],"package":"org.jenkins-ci.plugins:logstash","purl":"pkg:maven/org.jenkins-ci.plugins/logstash","source":"GHSA-5pg8-f89x-wjcx"}],"prev":{"headline":"Missing permission checks in Jenkins P4 Plugin","id":"CVE-2020-2142"},"products":["Jenkins Logstash 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 Logstash credentials in plain text via the Jenkins configuration form, exposing sensitive authentication data.","url":"https://insights.sbomify.com/CVE-2020-2143/"}