CVE-2022-1881
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 affected versions of Octopus Server an Insecure Direct Object Reference vulnerability exists where it is possible for a user to download Project Exports from a Project they do not have permissions to access. This vulnerability only impacts projects within the same 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 confidenceAn Insecure Direct Object Reference (IDOR) vulnerability in Octopus Server allows authenticated users to download Project Exports from projects they do not have permission to access. The vulnerability is limited to projects within the same Space, indicating a missing or inadequate authorization check on the project export endpoint.
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>= 2021.1.6959, < 2021.3.13021>= 2022.1.2121, < 2022.1.2894>= 2022.2.6729, < 2022.2.6971>= 2022.3.348, < 2022.3.2616CVSS 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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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.
-
Determine Octopus Server versionLog in to the Octopus Web UI, click Help in the top-right menu, and select About. Alternatively, query the API at /api/status or /api/serverversion endpoint.Affected if The installed version falls within any of these ranges: 2021.1.6959 to <2021.3.13021, 2022.1.2121 to <2022.1.2894, 2022.2.6729 to <2022.2.6971, or 2022.3.348 to <2022.3.2616
-
Verify Project Export feature existsNavigate to a project within a Space, then go to Settings > Export. Confirm the Export option is present and accessible in the project settings menu.Affected if The Project Export feature is available in the Octopus Server instance
-
Check user authentication and Space membershipLog in as a standard user who has access to at least one project in a Space. Verify they are not an admin but have basic project viewer permissions within that Space.Affected if You can authenticate as a non-admin user who is a member of a Space with multiple projects
-
Identify unauthorized project export possibilityAs an authenticated non-admin user in a Space, attempt to access the project export endpoint for a different project in the same Space where you lack explicit permissions. The vulnerable URL pattern is /api/{spaceId}/projects/{projectId}/export. Check if you can export a project you cannot view or manage.Affected if You can successfully download a Project Export from a project you do not have permission to access, as long as it is within the same Space
You are affected if your Octopus Server version is within the affected ranges listed and you have authenticated users in Spaces who can access the Project Export feature for projects outside their authorized scope.
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 · scoped2021.3.130212022.1.28942022.2.6971
Apply the vendor patch for CVE-2022-1881 and conduct a security review of all project-related endpoints to ensure proper authorization validation is enforced for resource access.
2022.3.2616 (or latest 2022.3 LTS), or respective fixed version for your branch: 2021.3.13021, 2022.1.2894, 2022.2.6971
- 1. Identify your current Octopus Server version by navigating to Configuration > About in the Octopus Web Portal
- 2. Determine which version branch your current installation falls into (2021.1.x, 2022.1.x, 2022.2.x, or 2022.3.x)
- 3. Plan your upgrade path: For 2021.1.x branch upgrade to 2021.3.13021 or later; for 2022.1.x branch upgrade to 2022.1.2894 or later; for 2022.2.x branch upgrade to 2022.2.6971 or later; for 2022.3.x branch upgrade to 2022.3.2616 or later
- 4. Take a full backup of your Octopus Server database and configuration before upgrading
- 5. Download the installer for your target fixed version from downloads.octopus.com
- 6. Run the installer on your Octopus Server node, following the standard upgrade procedure
- 7. If using a clustered configuration, upgrade the primary node first, then eachPoller node
- 8. Verify the upgrade was successful and test that Project Export permissions are correctly enforced
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,904.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-1881 — 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-1881 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