dbcve.org
Octopus ServerApplication · Octopus

CVE-2022-1901

MEDIUM · 5.3 CVSS v3.1 Published 2022-08-19
Fix available
A fix is available. Upgrade to 2022.1.3009 / 2022.2.7244 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click Patch available

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 · unedited
In affected versions of Octopus Deploy it is possible to unmask sensitive variables by using variable preview.

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
How this class of weakness works · CWE-269

Privileges are granted, or fail to be dropped, incorrectly, so an action runs with more power than it should. An attacker who reaches that path inherits the excess privilege. The fix is least-privilege throughout, with explicit, checked transitions whenever privilege changes.

General guidance for the improper privilege management class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

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
Octopus ServerApplication
Affected:>= 2019.1.0, <= 2019.7.3>= 2020.1.0, <= 2020.6.5449>= 2021.1.6959, <= 2021.3.13021>= 2022.1.0, < 2022.1.3009>= 2022.2.6729, < 2022.2.7244>= 2022.3.348, < 2022.3.4953

CVSS 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

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 · scoped
Upgrade available Upgrade to 2022.1.3009 / 2022.2.7244 / 2022.3.4953 or later
Fixed in 2022.1.30092022.2.72442022.3.4953
Vendor patch advisories.octopus.com →
Recommended fix High confidence

2022.1.3009 (or latest 2019.7.4+, 2020.6.5450+, 2021.3.13022+ depending on your release line)

  1. Identify your current Octopus Server version from the admin dashboard or about page
  2. Determine which version range your current installation falls into (2019.x, 2020.x, 2021.x, or 2022.x)
  3. Download the corresponding fixed version: For 2019.x line upgrade to 2019.7.4 or later; For 2020.x line upgrade to 2020.6.5450 or later; For 2021.x line upgrade to 2021.3.13022 or later; For 2022.1.x line upgrade to 2022.1.3009 or later
  4. Review Octopus Server upgrade prerequisites and backup procedures in official documentation
  5. Perform a backup of your Octopus Server database and configuration
  6. Execute the upgrade installer for the chosen fixed version
  7. Verify the upgrade was successful and test that sensitive variable preview functionality now properly masks values
  8. Consult the vendor advisory at https://advisories.octopus.com/post/2022/sa2022-09/ for any additional configuration requirements
Caveat Standard Octopus Server upgrade considerations apply - review release notes for your target version for any migration steps or deprecation notices

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,600. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-1901 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-1901 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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