What is the severity of CVE-2018-9039?

The severity of CVE-2018-9039 is considered medium due to its potential to expose sensitive machine information to unauthorized users.

How do I fix CVE-2018-9039?

To fix CVE-2018-9039, upgrade your Octopus Deploy installation to version 2018.3.7 or later.

Who is affected by CVE-2018-9039?

CVE-2018-9039 affects users of Octopus Deploy versions from 2.0 up to 2018.3.6 with variable edit permissions.

What are the implications of CVE-2018-9039?

The implications of CVE-2018-9039 allow authenticated users to view machines beyond the permissions of their team’s scoped environments.

Is CVE-2018-9039 a zero-day vulnerability?

CVE-2018-9039 is not a zero-day vulnerability as it was reported and patched after the affected versions were released.

Vulnerability/
CVE-2018-9039

medium

6.5

CWE

862

27/3/2018

5/8/2024

CVE-2018-9039

First published: Tue Mar 27 2018(Updated: )

In Octopus Deploy 2.0 and later before 2018.3.7, an authenticated user, with variable edit permissions, can scope some variables to targets greater than their permissions should allow. In other words, they can see machines beyond their team's scoped environments.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
Octopus Deploy	>=2.0<2018.3.7

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2018-9039?
The severity of CVE-2018-9039 is considered medium due to its potential to expose sensitive machine information to unauthorized users.
How do I fix CVE-2018-9039?
To fix CVE-2018-9039, upgrade your Octopus Deploy installation to version 2018.3.7 or later.
Who is affected by CVE-2018-9039?
CVE-2018-9039 affects users of Octopus Deploy versions from 2.0 up to 2018.3.6 with variable edit permissions.
What are the implications of CVE-2018-9039?
The implications of CVE-2018-9039 allow authenticated users to view machines beyond the permissions of their team’s scoped environments.
Is CVE-2018-9039 a zero-day vulnerability?
CVE-2018-9039 is not a zero-day vulnerability as it was reported and patched after the affected versions were released.

agent/references
agent/type
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/author
agent/weakness
agent/severity
agent/description
agent/first-publish-date
agent/event
agent/source
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
vendor/octopus
canonical/octopus deploy
version/octopus deploy/2.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-9039?
The severity of CVE-2018-9039 is considered medium due to its potential to expose sensitive machine information to unauthorized users.
How do I fix CVE-2018-9039?
To fix CVE-2018-9039, upgrade your Octopus Deploy installation to version 2018.3.7 or later.
Who is affected by CVE-2018-9039?
CVE-2018-9039 affects users of Octopus Deploy versions from 2.0 up to 2018.3.6 with variable edit permissions.
What are the implications of CVE-2018-9039?
The implications of CVE-2018-9039 allow authenticated users to view machines beyond the permissions of their team’s scoped environments.
Is CVE-2018-9039 a zero-day vulnerability?
CVE-2018-9039 is not a zero-day vulnerability as it was reported and patched after the affected versions were released.