{"answers":{"affected":"2 open source packages ship an affected version, including io.jenkins.plugins:chaos-monkey. It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-2323 in the wild and no public exploit code.","fix":"Upgrade io.jenkins.plugins:chaos-monkey to 0.4.1 or later.","what":"CVE-2020-2323 is a medium-severity missing authorization vulnerability in Jenkins Chaos Monkey Plugin, published on 3 Dec 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-2323 and fix it if it is affected.\n\nWhat it is: CVE-2020-2323 is a medium-severity missing authorization vulnerability in Jenkins Chaos Monkey Plugin, published on 3 Dec 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-2323 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- io.jenkins.plugins:chaos-monkey (Maven): affected all versions; fixed in 0.4.1\n- io.jenkins.plugins:chaos-monkey (Maven): affected all versions; fixed in 0.4.1\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-2323/ (Markdown: https://insights.sbomify.com/CVE-2020-2323/index.md)","id":"CVE-2020-2323","markdown":"https://insights.sbomify.com/CVE-2020-2323/index.md","name":"CVE-2020-2323","record":{"aliases":["GHSA-hx53-635r-vmv8"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Jenkins Chaos Monkey Plugin","requires_auth":"none","summary":"Attackers with read permissions can view Chaos Monkey action history due to missing permission checks in the plugin's HTTP endpoint.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"jenkins","cpe":[{"product":"chaos_monkey","vendor":"netflix"}],"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-862","name":"Missing Authorization"}],"description":"Jenkins Chaos Monkey Plugin 0.4 and earlier does not perform permission checks in an HTTP endpoint, allowing attackers with Overall/Read permission to access the Chaos Monkey page and to see the history of actions.","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":"Missing permission checks in Jenkins Chaos Monkey Plugin","id":"CVE-2020-2323","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"missing_authorization","year":"2020"},"n_packages":2,"n_references":2,"next":{"headline":"XXE vulnerability in Jenkins CVS Plugin","id":"CVE-2020-2324"},"packages":[{"ecosystem":"Maven","fixed":["0.4.1"],"introduced":["0"],"last_affected":[],"package":"io.jenkins.plugins:chaos-monkey","purl":null,"source":"GHSA-hx53-635r-vmv8"},{"ecosystem":"Maven","fixed":["0.4.1"],"introduced":["0"],"last_affected":[],"package":"io.jenkins.plugins:chaos-monkey","purl":"pkg:maven/io.jenkins.plugins/chaos-monkey","source":"GHSA-hx53-635r-vmv8"}],"prev":{"headline":"Missing permission checks in Jenkins Chaos Monkey Plugin","id":"CVE-2020-2322"},"products":["Jenkins Chaos Monkey Plugin"],"published":"2020-12-03","related":[{"cvss_score":7.5,"headline":"Missing permission checks in Jenkins Chaos Monkey Plugin","id":"CVE-2020-2322","kev_date_added":null,"published":"2020-12-03"}],"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 permissions can view Chaos Monkey action history due to missing permission checks in the plugin's HTTP endpoint.","url":"https://insights.sbomify.com/CVE-2020-2323/"}