CVE-2022-2828
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 it is possible to reveal information about teams via the API due to an Insecure Direct Object Reference (IDOR) vulnerability
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 · moderate confidenceThis is an Insecure Direct Object Reference (IDOR) vulnerability in Octopus Server's API that allows authenticated users to access team information they shouldn't be authorized to view by manipulating object references (team IDs). The vulnerability enables unauthorized information disclosure about teams through direct API calls.
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.2121, <= 2022.1.3135>= 2022.2.0, <= 2022.2.7897>= 2022.3.0, <= 2022.3.10586CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Identify Octopus Server versionCheck the installed Octopus Server version. In the web UI, this is typically shown in the footer of any page or in the 'About' section. Alternatively, access the API endpoint /api/system/health or check the installation directory for version information.Affected if The installed version falls within any of these ranges: 2022.1.2121 through 2022.1.3135, 2022.2.0 through 2022.2.7897, or 2022.3.0 through 2022.3.10586.
-
Confirm API access is enabledVerify that the Octopus Server API is accessible. The API is typically available at the /api endpoint. Ensure the server is running and responding to HTTP requests.Affected if The API is accessible without being explicitly disabled (API is enabled by default in Octopus Server).
-
Review team API endpoint authorizationTest the team API endpoint by making an authenticated request to /api/teams with a valid user account that has limited permissions. Attempt to access team resources using different team IDs to see if unauthorized data is returned.Affected if A user without proper team permissions can retrieve team information by manipulating team ID values in API requests, indicating the IDOR vulnerability is present.
-
Check audit logs for unauthorized team accessReview Octopus Server audit logs for any suspicious access patterns where users accessed team resources outside their assigned permissions. Look in the Audit section of the UI or via the /api/audit endpoint.Affected if Audit logs show team information was accessed by users who should not have authorization to view those specific teams.
You are affected if your Octopus Server version is within any of the three affected version ranges AND the API team endpoints allow unauthorized access to team data via manipulated object references.
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.
From vendor dataApply the vendor patch for affected Octopus Server versions and implement proper authorization validation on API endpoints to verify user permissions before returning team data.
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-2828 — 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-2828 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