CVE-2024-4811
First published: Thu Jul 25 2024(Updated: )
In affected versions of Octopus Server under certain conditions, a user with specific role assignments can access restricted project artifacts.
Credit: security@octopus.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Octopus Deploy |
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-2024-4811?
CVE-2024-4811 has been classified with a moderate severity level due to unauthorized access potential.
How do I fix CVE-2024-4811?
To fix CVE-2024-4811, ensure that role assignments are properly configured to restrict access to project artifacts.
What versions of Octopus Server are affected by CVE-2024-4811?
CVE-2024-4811 affects specific versions of Octopus Server where certain role conditions are met.
Can CVE-2024-4811 lead to data breaches?
Yes, CVE-2024-4811 can potentially lead to data breaches if project artifacts are accessed by unauthorized users.
What should I do if I suspect my Octopus Server is affected by CVE-2024-4811?
If you suspect your Octopus Server is affected by CVE-2024-4811, review your role assignments and consider applying the recommended fixes immediately.
- agent/references
- agent/first-publish-date
- agent/description
- agent/type
- agent/severity
- agent/author
- collector/nvd-api
- source/NVD
- agent/weakness
- agent/event
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/source
- agent/softwarecombine
- agent/tags
- agent/guess-ai
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- vendor/octopus deploy
- canonical/octopus deploy