dbcve.org
Octopus ServerApplication · Octopus

CVE-2022-29890

MEDIUM · 6.1 CVSS v3.1 Published 2022-07-15
Fix available
A fix is available. Upgrade to 2021.3.13021 / 2022.1.2849 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 Server the help sidebar can be customized to include a Cross-Site Scripting payload in the support link.

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 confidence

Octopus Server's help sidebar customization feature does not properly sanitize the support link field, allowing stored XSS. An attacker with administrative access can inject malicious JavaScript that executes when other users view the help sidebar.

MitigationApply the vendor-provided security patch for this vulnerability. Until patched, restrict administrative access to the help sidebar customization and monitor for suspicious links.

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
Octopus ServerApplication
Affected:>= 2019.7.0, < 2021.3.13021>= 2022.1.2121, < 2022.1.2849>= 2022.3.348, < 2022.3.2387= 2022.2.6729

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Octopus Server version
    Navigate to the Octopus Web UI, click your username in the top-right corner, and select 'About' to view the server version. Alternatively, check the installation directory or use PowerShell: Get-ItemProperty -Path 'HKLM:\SOFTWARE\Octopus' | Select-Object DisplayVersion
    Affected if The installed version falls within any of these ranges: >= 2019.7.0 and < 2021.3.13021; >= 2021.3.2121 and < 2022.1.2849; >= 2022.3.348 and < 2022.3.2387; or equals exactly 2022.2.6729
  2. Determine if help sidebar customization is accessible
    Log in as an administrator and navigate to Configuration > General > Help menu customization, or access the help sidebar settings panel. Check whether the 'Support link' or similar URL field is present and editable.
    Affected if The help sidebar customization feature is enabled and the user has administrative access to modify the support link field
  3. Inspect the current support link configuration
    As an administrator, view the current value in the Support link field within the help sidebar customization settings. Look for unusual URL patterns, encoded characters, or javascript: prefixes that may indicate injected code.
    Affected if The Support link field contains unexpected values such as javascript: scripts, HTML tags, or URLs that do not point to a legitimate support resource
  4. Review help sidebar usage in logs
    Check Octopus Server logs (located in the_logs folder) for entries involving the help sidebar or help menu endpoints. Look for unusual or repeated requests that may indicate exploitation attempts.
    Affected if Logs show unexpected script content in help sidebar requests or unusual patterns of access to the customization endpoints

A user is affected if their Octopus Server version is within the affected ranges AND the help sidebar customization feature is accessible to administrators with the ability to modify the support link field.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 2021.3.13021 / 2022.1.2849 / 2022.3.2387 or later
Fixed in 2021.3.130212022.1.28492022.3.2387
Interim mitigation

Apply the vendor-provided security patch for this vulnerability. Until patched, restrict administrative access to the help sidebar customization and monitor for suspicious links.

Recommended fix High confidence

2022.3.2387 or later (or 2021.3.13021 for 2019.7.0-2021.2.x users, 2022.1.2849 for 2022.1.x users)

  1. Backup your Octopus Server database and configuration
  2. Check current version in Octopus: go to Configuration > About
  3. Plan upgrade during a maintenance window with downtime
  4. Download the appropriate installer for version 2022.3.2387 or later from octopus.com/downloads
  5. Stop the Octopus Server service
  6. Run the installer and follow the upgrade wizard
  7. After installation, verify the service starts successfully
  8. Log in to Octopus and navigate to Configuration > About to confirm version 2022.3.2387 or later is installed
Caveat Review Octopus release notes for any migration steps required between major version jumps; test in staging first

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

Fix this in Octopus Server Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-29890 — 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-29890 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