CVE-2018-4862
First published: Wed Jan 03 2018(Updated: )
In Octopus Deploy versions 3.2.11 - 4.1.5 (fixed in 4.1.6), an authenticated user with ProcessEdit permission could reference an Azure account in such a way as to bypass the scoping restrictions, resulting in a potential escalation of privileges.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Octopus Deploy | >=3.2.11<=4.1.5 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2018-4862?
CVE-2018-4862 has a severity rating that indicates a significant risk of privilege escalation for affected users.
How do I fix CVE-2018-4862?
To fix CVE-2018-4862, upgrade Octopus Deploy to version 4.1.6 or later.
What versions of Octopus Deploy are affected by CVE-2018-4862?
CVE-2018-4862 affects Octopus Deploy versions 3.2.11 through 4.1.5.
Who is at risk for CVE-2018-4862?
Authenticated users with ProcessEdit permission in Octopus Deploy are at risk for CVE-2018-4862.
Can CVE-2018-4862 lead to unauthorized access?
Yes, CVE-2018-4862 may allow an authenticated user to escalate their privileges, potentially leading to unauthorized access.
- agent/type
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- agent/references
- agent/severity
- agent/author
- agent/last-modified-date
- agent/weakness
- 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/3.2.11
- version/octopus deploy/4.1.5