CVE-2022-48310
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 · uneditedAn information disclosure vulnerability allows sensitive key material to be included in technical support archives in Sophos Connect versions older than 2.2.90.
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 confidenceAn information disclosure vulnerability in Sophos Connect versions prior to 2.2.90 allows sensitive cryptographic key material to be inadvertently included in technical support archives generated by the product, potentially exposing credentials to unauthorized parties who obtain the support files.
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< 2.2.90CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/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.
-
Confirm Sophos Connect installationCheck if Sophos Connect is installed on the system. On Windows, look for the application in Program Files or Program Files (x86), or check the Windows Registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for an entry named Sophos Connect. On macOS, check /Applications for Sophos Connect.app.Affected if Sophos Connect is not installed on the system
-
Identify installed versionLocate the Sophos Connect version information. On Windows, right-click the Sophos Connect icon in the system tray and select 'About' or 'Help' > 'About', or check the Windows Registry under HKLM\SOFTWARE\Sophos\Connect for a Version value. On macOS, right-click Sophos Connect.app in Applications and select 'Get Info' to view the version.Affected if The displayed version number is lower than 2.2.90
-
Compare against vulnerable rangeCompare the identified version number to the affected range: any version prior to 2.2.90 is vulnerable. Version 2.2.90 and later are not affected.Affected if Installed version is 2.2.89 or earlier
The environment is affected if Sophos Connect is installed and the version is below 2.2.90, as this version range includes sensitive cryptographic key material in generated support archives.
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.
dbcve · scoped2.2.90
Upgrade Sophos Connect to version 2.2.90 or later to prevent sensitive key material from being included in support archives.
2.2.90
- Identify the current version of Sophos Connect installed on the system
- Verify if the installed version is older than 2.2.90
- If vulnerable, download Sophos Connect version 2.2.90 or later from the official Sophos support website
- Install the updated version following standard Sophos installation procedures
- Verify the upgrade was successful by checking the newly installed version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-48310 — 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-48310 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