CVE-2022-3614
First published: Tue Jan 03 2023(Updated: )
In affected versions of Octopus Deploy users of certain browsers using AD to sign-in to Octopus Server were able to bypass authentication checks and be redirected to the configured redirect url without any validation.
Credit: security@octopus.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Octopus Deploy | >=3.5<2022.3.10750 | |
| Octopus Deploy | >=2022.4<2022.4.8063 |
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-2022-3614?
CVE-2022-3614 has a severity rating of medium due to the potential for authentication bypass in affected versions.
How do I fix CVE-2022-3614?
To fix CVE-2022-3614, upgrade Octopus Deploy to version 2022.4.8064 or later.
Which versions of Octopus Deploy are affected by CVE-2022-3614?
CVE-2022-3614 affects Octopus Deploy versions from 3.5 up to 2022.3.10750 and from 2022.4 up to 2022.4.8063.
Can CVE-2022-3614 be exploited remotely?
Yes, CVE-2022-3614 can be exploited remotely if a user utilizes specific browsers to sign in.
What are the implications of CVE-2022-3614 for organizations?
Organizations using affected versions of Octopus Deploy may face unauthorized access risks due to bypassed authentication checks.
- agent/type
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- agent/severity
- agent/references
- agent/weakness
- agent/author
- agent/last-modified-date
- 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.5
- version/octopus deploy/2022.4