dbcve.org
ConnectApplication · Sophos

CVE-2022-4901

MEDIUM · 6.1 CVSS v3.1 Published 2023-03-01
Fix available
A fix is available. Upgrade to 2.2.90 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
Multiple stored XSS vulnerabilities in Sophos Connect versions older than 2.2.90 allow Javascript code to run in the local UI via a malicious VPN configuration that must be manually loaded by the victim.

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

Stored XSS vulnerability in Sophos Connect VPN client allows malicious JavaScript execution in the local UI through a crafted VPN configuration file. The victim must manually import the malicious configuration, causing the embedded JavaScript to execute when the configuration is viewed or processed by the application.

MitigationUpgrade Sophos Connect to version 2.2.90 or later to remediate the vulnerability. Additionally, enforce policy prohibiting loading VPN configurations from untrusted or unverified sources.

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
ConnectApplication
Affected:< 2.2.90

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. Verify Sophos Connect installation
    Check if Sophos Connect client is installed on the system by searching for the application in installed programs or running 'sophos-connect --version' if available via command line
    Affected if Sophos Connect is not installed on the system
  2. Identify installed Sophos Connect version
    Locate the installed version of Sophos Connect through the application itself (typically in Help > About or the application UI), or check program files for version information
    Affected if The installed version is lower than 2.2.90 (e.g., 2.2.89, 2.2.0, 1.x series)
  3. Review imported VPN configurations
    Access the Sophos Connect client interface and examine the list of imported VPN configuration profiles or connection profiles
    Affected if Any VPN configuration files have been imported into the client
  4. Inspect configuration file source
    Check if any imported VPN configurations originated from untrusted or unverified sources, or if the configuration file was obtained from an unfamiliar or external party
    Affected if Configurations were imported from untrusted or unknown sources

A system is affected if Sophos Connect version is below 2.2.90 AND a malicious VPN configuration file has been imported, enabling stored XSS execution when the configuration is viewed or processed.

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 2.2.90 or later
Fixed in 2.2.90
Interim mitigation

Upgrade Sophos Connect to version 2.2.90 or later to remediate the vulnerability. Additionally, enforce policy prohibiting loading VPN configurations from untrusted or unverified sources.

Recommended fix High confidence

Sophos Connect version 2.2.90 or later

  1. Check the current installed version of Sophos Connect by opening the application and navigating to Help > About
  2. Download Sophos Connect version 2.2.90 or later from the official Sophos download portal at www.sophos.com
  3. Run the installer and follow the on-screen prompts to upgrade Sophos Connect
  4. After upgrade completes, verify the version by checking Help > About to confirm version 2.2.90 or higher is installed

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

Fix this in Connect Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,900
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,040.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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