CVE-2018-4862: High severity octopus deploy vulnerability
Published Jan 3, 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.
Affected Software
1 affected component
Octopus Octopus Deploy>=3.2.11<=4.1.5
Event History
Jan 3, 2018
CVE Published
via MITRE·09:00 AM
Data Sourced
via MITRE·09:00 AM
Description
Frequently Asked Questions
1
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.
2
How do I fix CVE-2018-4862?
To fix CVE-2018-4862, upgrade Octopus Deploy to version 4.1.6 or later.
3
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.
4
Who is at risk for CVE-2018-4862?
Authenticated users with ProcessEdit permission in Octopus Deploy are at risk for CVE-2018-4862.
5
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.