{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-11320 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-11320 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-11320 is a critical vulnerability in Octopus Octopus Server, published on 21 May 2018. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-11320 and fix it if it is affected.\n\nWhat it is: CVE-2018-11320 is a critical vulnerability in Octopus Octopus Server, published on 21 May 2018. 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-2018-11320 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-2018-11320/ (Markdown: https://insights.sbomify.com/CVE-2018-11320/index.md)","id":"CVE-2018-11320","markdown":"https://insights.sbomify.com/CVE-2018-11320/index.md","name":"CVE-2018-11320","record":{"aliases":["GHSA-j5f8-rc75-mmgw"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Deployment automation server","requires_auth":"none","summary":"Attackers can view sensitive Octopus variables in deployment logs because they are not obfuscated, exposing secrets to anyone with log access.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"octopus_server","vendor":"octopus"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-532","name":"Insertion of Sensitive Information into Log File"}],"description":"In Octopus Deploy 2018.4.4 through 2018.5.1, Octopus variables that are sourced from the target do not have sensitive values obfuscated in the deployment logs.","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-2018-11320","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"octopus:octopus_server","products":["octopus:octopus_server"],"type":"information_disclosure","year":"2018"},"n_packages":0,"n_references":1,"next":{"headline":"Code injection in n/a","id":"CVE-2018-11321"},"packages":[],"prev":{"headline":"Path traversal in n/a","id":"CVE-2018-11319"},"products":["n/a"],"published":"2018-05-21","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.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-09-16","vendors":["n/a"]},"summary":"Attackers can view sensitive Octopus variables in deployment logs because they are not obfuscated, exposing secrets to anyone with log access.","url":"https://insights.sbomify.com/CVE-2018-11320/"}