{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2020-16197 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-16197 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-16197 is a medium-severity missing authorization vulnerability in Octopus Octopus Server, published on 25 Aug 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-16197 and fix it if it is affected.\n\nWhat it is: CVE-2020-16197 is a medium-severity missing authorization vulnerability in Octopus Octopus Server, published on 25 Aug 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-16197 in the wild and no public exploit code.\n\nAffected product: Octopus Octopus Server. 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-16197/ (Markdown: https://insights.sbomify.com/CVE-2020-16197/index.md)","id":"CVE-2020-16197","markdown":"https://insights.sbomify.com/CVE-2020-16197/index.md","name":"CVE-2020-16197","record":{"aliases":["GHSA-w4vm-8m9w-5qwm"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Octopus Deploy","requires_auth":"low_privilege","summary":"Authorized users can bypass scope validation to access unauthorized certificates and metadata in Octopus Deploy.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"octopus_server","vendor":"octopus"},{"product":"server","vendor":"octopus"}],"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-295","name":"Improper Certificate Validation"}],"description":"An issue was discovered in Octopus Deploy 3.4. A deployment target can be configured with an Account or Certificate that is outside the scope of the deployment target. An authorised user can potentially use a certificate that they are not in scope to use. An authorised user is also able to obtain certificate metadata by associating a certificate with certain resources that should fail scope validation.","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":"Missing authorization in n/a","id":"CVE-2020-16197","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"octopus:octopus_server","products":["octopus:octopus_server"],"type":"missing_authorization","year":"2020"},"n_packages":0,"n_references":3,"next":{"headline":"Philips Clinical Collaboration Platform Protection Mechanism Failure","id":"CVE-2020-16198"},"packages":[],"prev":{"headline":"DO NOT USE THIS CANDIDATE NUMBER.","id":"CVE-2020-16196"},"products":["n/a"],"published":"2020-08-25","related":[{"cvss_score":9.8,"headline":"Auth bypass in Octopus Server","id":"CVE-2022-2572","kev_date_added":null,"published":"2022-11-01"},{"cvss_score":9.8,"headline":"Security feature bypass in Octopus Server","id":"CVE-2022-2778","kev_date_added":null,"published":"2022-09-30"},{"cvss_score":9.8,"headline":"Information disclosure in n/a","id":"CVE-2018-11320","kev_date_added":null,"published":"2018-05-21"},{"cvss_score":9.1,"headline":"Auth bypass in Octopus Server","id":"CVE-2022-2782","kev_date_added":null,"published":"2022-10-26"},{"cvss_score":8.8,"headline":"Race condition in Octopus Server","id":"CVE-2024-2975","kev_date_added":null,"published":"2024-04-09"},{"cvss_score":8.8,"headline":"Command injection in Octopus Server","id":"CVE-2022-4009","kev_date_added":null,"published":"2023-03-16"},{"cvss_score":8.8,"headline":"Code injection in n/a","id":"CVE-2018-18850","kev_date_added":null,"published":"2018-10-31"}],"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":"Authorized users can bypass scope validation to access unauthorized certificates and metadata in Octopus Deploy.","url":"https://insights.sbomify.com/CVE-2020-16197/"}