{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-18850 exists.","fix":"No fix has been published for CVE-2018-18850 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-18850 is a high-severity code injection vulnerability in Octopus Octopus Server, published on 31 Oct 2018. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-18850 and fix it if it is affected.\n\nWhat it is: CVE-2018-18850 is a high-severity code injection vulnerability in Octopus Octopus Server, published on 31 Oct 2018. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-18850 exists.\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-18850/ (Markdown: https://insights.sbomify.com/CVE-2018-18850/index.md)","id":"CVE-2018-18850","markdown":"https://insights.sbomify.com/CVE-2018-18850/index.md","name":"CVE-2018-18850","record":{"aliases":["GHSA-483m-372f-vxc5"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["code_execution","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"Octopus Deploy","requires_auth":"low_privilege","summary":"Authenticated users with deployment permissions can upload malicious YAML to execute arbitrary code with SYSTEM privileges on the Octopus Server.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"octopus_server","vendor":"octopus"}],"cvss":{"score":8.8,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[],"description":"In Octopus Deploy 2018.8.0 through 2018.9.x before 2018.9.1, an authenticated user with permission to modify deployment processes could upload a maliciously crafted YAML configuration, potentially allowing for remote execution of arbitrary code, running in the same context as the Octopus Server (for self-hosted installations by default, SYSTEM).","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2017-05-15","github_poc":0,"max_poc_stars":null,"metasploit":1,"nuclei":0,"refs":[{"date":"2017-05-15","kind":"metasploit","ref":"exploit/windows/http/octopusdeploy_deploy","stars":null,"title":"Octopus Deploy Authenticated Code Execution"}],"tier":"weaponised"},"has_fix":null,"headline":"Code injection in n/a","id":"CVE-2018-18850","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"octopus:octopus_server","products":["octopus:octopus_server"],"type":"code_injection","year":"2018"},"n_packages":0,"n_references":1,"next":{"headline":"Command injection in n/a","id":"CVE-2018-18852"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2018-18849"},"products":["n/a"],"published":"2018-10-31","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"}],"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":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"attribution","licence":"BSD-3-Clause","name":"Metasploit"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Authenticated users with deployment permissions can upload malicious YAML to execute arbitrary code with SYSTEM privileges on the Octopus Server.","url":"https://insights.sbomify.com/CVE-2018-18850/"}