New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remote Code Execution via malicious YAML configurations in some versions #5042

Closed
jburger opened this Issue Oct 30, 2018 · 4 comments

Comments

Projects
None yet
3 participants
@jburger

jburger commented Oct 30, 2018

Description

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

If this issue is of concern to you and your team, we strongly recommend upgrading to version 2018.9.1.

CVE-2018-18850

Affected versions

Octopus Server:
versions 2018.8.0-2018.9.0, inclusive.

Mitigation

In any version affected by this issue, we recommend upgrading to version 2018.9.1.

Workarounds

In situations where upgrade is not possible, running the octopus server built in worker as a service account with limited privileges may help to minimize the potential impact of such an occurrence, however this will not prevent attackers from attempting to chain other attacks against the server.

https://octopus.com/docs/administration/security/hardening-octopus#prevent-user-provided-scripts-from-doing-harm

https://octopus.com/docs/administration/workers/built-in-worker#running-tasks-on-the-octopus-server-as-a-different-user

@jburger

This comment has been minimized.

@attritionorg

This comment has been minimized.

attritionorg commented Oct 31, 2018

@jburger that is 404 or requires auth. is there a copy of that somewhere free for anyone to see?

@matt-richardson

This comment has been minimized.

Contributor

matt-richardson commented Oct 31, 2018

@attritionorg - that's just a link to the internal trello card we use for tracking. Nothing interesting.

@attritionorg

This comment has been minimized.

attritionorg commented Oct 31, 2018

@matt-richardson gotcha thanks!

@jburger jburger closed this Nov 4, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment