What is the severity of CVE-2018-18850?

CVE-2018-18850 is considered a high severity vulnerability due to its potential for remote code execution.

How do I fix CVE-2018-18850?

To fix CVE-2018-18850, update Octopus Deploy to version 2018.9.1 or later.

Who is affected by CVE-2018-18850?

CVE-2018-18850 affects authenticated users of Octopus Deploy versions 2018.8.0 to 2018.9.0.

What actions can an attacker perform with CVE-2018-18850?

An attacker can upload a malicious YAML configuration that allows for the execution of arbitrary code.

Vulnerability/
CVE-2018-18850

critical

31/10/2018

5/8/2024

CVE-2018-18850

Q: Is access control relevant in CVE-2018-18850?

Yes, an authenticated user with permission to modify deployment processes can exploit CVE-2018-18850.

First published: Wed Oct 31 2018(Updated: )

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).

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
Octopus Deploy	>=2018.8.0<=2018.8.12
Octopus Deploy	>=2018.9.0<2018.9.1

Never miss a vulnerability like this again

Reference Links

https://github.com/OctopusDeploy/Issues/issues/5042

Frequently Asked Questions

What is the severity of CVE-2018-18850?
CVE-2018-18850 is considered a high severity vulnerability due to its potential for remote code execution.
How do I fix CVE-2018-18850?
To fix CVE-2018-18850, update Octopus Deploy to version 2018.9.1 or later.
Who is affected by CVE-2018-18850?
CVE-2018-18850 affects authenticated users of Octopus Deploy versions 2018.8.0 to 2018.9.0.
What actions can an attacker perform with CVE-2018-18850?
An attacker can upload a malicious YAML configuration that allows for the execution of arbitrary code.
Is access control relevant in CVE-2018-18850?
Yes, an authenticated user with permission to modify deployment processes can exploit CVE-2018-18850.

agent/type
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/references
agent/last-modified-date
agent/author
agent/severity
agent/event
agent/description
agent/first-publish-date
agent/source
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
vendor/octopus
canonical/octopus deploy
version/octopus deploy/2018.8.0
version/octopus deploy/2018.8.12
version/octopus deploy/2018.9.0

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of CVE-2018-18850?
CVE-2018-18850 is considered a high severity vulnerability due to its potential for remote code execution.
How do I fix CVE-2018-18850?
To fix CVE-2018-18850, update Octopus Deploy to version 2018.9.1 or later.
Who is affected by CVE-2018-18850?
CVE-2018-18850 affects authenticated users of Octopus Deploy versions 2018.8.0 to 2018.9.0.
What actions can an attacker perform with CVE-2018-18850?
An attacker can upload a malicious YAML configuration that allows for the execution of arbitrary code.
Is access control relevant in CVE-2018-18850?
Yes, an authenticated user with permission to modify deployment processes can exploit CVE-2018-18850.