dbcve.org
Octopus ServerApplication · Octopus

CVE-2022-4898

MEDIUM · 5.4 CVSS v3.1 Published 2023-01-31
Fix available
A fix is available. Upgrade to 2022.2.8552 / 2022.3.10750 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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. This was initially resolved in advisory 2022-07 however it was identified that the fix could be bypassed in certain circumstances. A different approach was taken to prevent the possibility of the support link being susceptible to XSS

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 contains a stored Cross-Site Scripting (XSS) vulnerability in the help sidebar's customizable support link. An initial fix released in the 2022-07 advisory was found to be bypassable under certain conditions, requiring an alternative remediation approach to properly sanitize and prevent XSS execution.

MitigationApply the vendor-provided patch or update to a version that contains the revised fix for the support link XSS vulnerability.

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, < 2022.2.8552>= 2022.3.348, < 2022.3.10750>= 2022.4.791, < 2022.4.8319

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

CVSS:3.1/AV:N/AC:L/PR:L/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 Octopus Server version
    Log into the Octopus Web UI and navigate to the Configuration page, or check the server's About page (typically at /about). The version is displayed there.
    Affected if The installed version falls within any of these ranges: >= 2019.7.0 and < 2022.2.8552; OR >= 2022.3.348 and < 2022.3.10750; OR >= 2022.4.791 and < 2022.4.8319
  2. Locate the help sidebar support link configuration
    In the Octopus Web UI, go to Configuration > General Settings > Support link. This is where administrators configure the customizable support link shown in the help sidebar.
    Affected if A custom support link URL has been configured in this field (the vulnerability only applies when a custom link is set)
  3. Inspect the configured support link URL
    Examine the Support Link field value in Configuration > General Settings. Look for any URL that contains HTML special characters, JavaScript event handlers, or unusual encoding that could indicate attempted injection.
    Affected if The configured URL contains characters such as javascript:, onload=, onerror=, or other HTML/script injection patterns

You are affected if your Octopus Server version is within any of the affected ranges AND a custom support link has been configured in the help sidebar settings.

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 2022.2.8552 / 2022.3.10750 / 2022.4.8319 or later
Fixed in 2022.2.85522022.3.107502022.4.8319
Interim mitigation

Apply the vendor-provided patch or update to a version that contains the revised fix for the support link XSS vulnerability.

Recommended fix High confidence

2022.2.8552 (or later 2022.2.x) | 2022.3.10750 (or later 2022.3.x) | 2022.4.8319 (or later 2022.4.x)

  1. Identify current Octopus Server version via the UI (Help > About) or via API endpoint /api/serverinfo
  2. For 2022.2.x branch: upgrade to version 2022.2.8552 or later
  3. For 2022.3.x branch: upgrade to version 2022.3.10750 or later
  4. For 2022.4.x branch: upgrade to version 2022.4.8319 or later
  5. After upgrade, verify the help sidebar support link renders as plain text and does not execute any JavaScript

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

Fix this in Octopus Server Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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