CVE-2022-2013
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIn Octopus Server after version 2022.1.1495 and before 2022.1.2647 if private spaces were enabled via the experimental feature flag all new users would have access to the Script Console within their private space.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceIn Octopus Server versions 2022.1.1496 through 2022.1.2646, enabling the experimental private spaces feature incorrectly granted all new users elevated access to the Script Console within their private space, allowing potential execution of arbitrary scripts.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 2022.1.1495, < 2022.1.2647CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check Octopus Server versionNavigate to the Octopus UI: Go to Configuration > About, or use the API endpoint /api/about. Locate the version number displayed.Affected if The installed version is >= 2022.1.1495 AND < 2022.1.2647
-
Verify if private spaces experimental feature is enabledNavigate to Configuration > Features > Experimental Features in the Octopus UI. Look for the 'Private Spaces' feature toggle or checkbox.Affected if The Private Spaces experimental feature is turned ON or enabled
-
Confirm new user Script Console access existsNavigate to a space where a newly created user account exists. Go to that space's settings and check the user's permissions, specifically looking for Script Console access within the space.Affected if Newly created users in a private space have Script Console permissions enabled when they should not
You are affected if your Octopus Server version falls between 2022.1.1495 and 2022.1.2646 AND the experimental Private Spaces feature is currently enabled, causing new users to have unintended Script Console access.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped2022.1.2647
Upgrade Octopus Server to version 2022.1.2647 or later. If immediate upgrade is not feasible, disable the private spaces experimental feature until the upgrade can be performed.
2022.1.2647 or later
- Backup your Octopus Deploy database and configuration
- Stop the Octopus Deploy Server service
- Download Octopus Deploy version 2022.1.2647 or later from octopus.com/downloads
- Run the installer or deploy the new version to upgrade your Octopus Deploy Server
- Start the Octopus Deploy Server service
- Verify that the Script Console access is properly restricted in private spaces
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-2013 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-2013 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data