{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-24566 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-24566 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-24566 is a high-severity vulnerability in n/a, published on 9 Sep 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-24566 and fix it if it is affected.\n\nWhat it is: CVE-2020-24566 is a high-severity vulnerability in n/a, published on 9 Sep 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-24566 in the wild and no public exploit code.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-24566/ (Markdown: https://insights.sbomify.com/CVE-2020-24566/index.md)","id":"CVE-2020-24566","markdown":"https://insights.sbomify.com/CVE-2020-24566/index.md","name":"CVE-2020-24566","record":{"aliases":["GHSA-jmmv-5xg4-p56f"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"Octopus Deploy","requires_auth":"none","summary":"Authenticated users can expose Azure account passwords in cleartext within verbose task logs when configuring specific deployment steps.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"octopus_deploy","vendor":"octopus"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-532","name":"Insertion of Sensitive Information into Log File"}],"description":"In Octopus Deploy 2020.3.x before 2020.3.4 and 2020.4.x before 2020.4.1, if an authenticated user creates a deployment or runbook process using Azure steps and sets the step's execution location to run on the server/worker, then (under certain circumstances) the account password is exposed in cleartext in the verbose task logs output.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Information disclosure in n/a","id":"CVE-2020-24566","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2020"},"n_packages":0,"n_references":2,"next":{"headline":"Privilege escalation in n/a","id":"CVE-2020-24567"},"packages":[],"prev":{"headline":"Information disclosure in Trend Micro Apex One","id":"CVE-2020-24565"},"products":["n/a"],"published":"2020-09-09","related":[{"cvss_score":8.8,"headline":"Privilege escalation in n/a","id":"CVE-2020-10678","kev_date_added":null,"published":"2020-03-19"},{"cvss_score":8.8,"headline":"An issue was discovered in Octopus Deploy before 4.1.9.","id":"CVE-2018-5706","kev_date_added":null,"published":"2018-01-16"},{"cvss_score":8.8,"headline":"Privilege escalation in n/a","id":"CVE-2018-4862","kev_date_added":null,"published":"2018-01-03"},{"cvss_score":8.8,"headline":"Missing authorization in n/a","id":"CVE-2017-17665","kev_date_added":null,"published":"2017-12-13"},{"cvss_score":8.1,"headline":"Missing authorization in n/a","id":"CVE-2019-11632","kev_date_added":null,"published":"2019-05-01"},{"cvss_score":7.8,"headline":"Privilege escalation in Octopus Server","id":"CVE-2021-26556","kev_date_added":null,"published":"2021-10-07"},{"cvss_score":7.5,"headline":"Missing authorization in Octopus Server","id":"CVE-2022-2013","kev_date_added":null,"published":"2022-06-12"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":["n/a"]},"summary":"Authenticated users can expose Azure account passwords in cleartext within verbose task logs when configuring specific deployment steps.","url":"https://insights.sbomify.com/CVE-2020-24566/"}