dbcve.org
Unified Threat ManagementApplication · Sophos

CVE-2022-0386

HIGH · 8.8 CVSS v3.1 Published 2022-03-22
Fix available
A fix is available. Upgrade to 9.710 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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
A post-auth SQL injection vulnerability in the Mail Manager potentially allows an authenticated attacker to execute code in Sophos UTM before version 9.710.

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 · high confidence

A post-authentication SQL injection vulnerability in the Mail Manager component of Sophos UTM allows an authenticated attacker to inject malicious SQL queries, potentially leading to arbitrary code execution on the affected system. The vulnerability stems from insufficient input sanitization in SQL queries within the Mail Manager module.

MitigationUpgrade Sophos UTM to version 9.710 or later to receive the vendor patch. If immediate patching is not feasible, restrict access to the Mail Manager administrative interface to trusted IPs only and monitor for suspicious SQL patterns in logs.

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
Unified Threat ManagementApplication
Affected:< 9.710

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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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 Sophos UTM installation
    Check if Sophos UTM (Unified Threat Management) is deployed in your environment. This is typically a network security appliance or virtual appliance.
    Affected if Sophos UTM is present in the environment
  2. Determine installed Sophos UTM version
    Access the appliance administration interface and navigate to System > Backup > Firmware, or use the command line and run 'version' or check /etc/version to retrieve the installed firmware version.
    Affected if The installed version is below 9.710 (for example, 9.700, 9.600, or earlier)
  3. Verify Mail Manager module is active
    Log into the Sophos UTM administrative web interface and navigate to the Mail Manager section (typically under Email > Mail Manager) to confirm the module is configured and enabled.
    Affected if Mail Manager is enabled and accessible via the web interface
  4. Review logs for suspicious SQL patterns
    Examine Mail Manager and system logs for unusual SQL syntax, unexpected database error messages, or SQL injection attempt indicators. Check logs under /var/log or via the Log Viewer in the admin interface.
    Affected if Unexpected SQL syntax, database errors, or anomalous queries appear in Mail Manager logs

You are affected if Sophos UTM with Mail Manager enabled is running a version lower than 9.710.

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

Upgrade Sophos UTM to version 9.710 or later to receive the vendor patch. If immediate patching is not feasible, restrict access to the Mail Manager administrative interface to trusted IPs only and monitor for suspicious SQL patterns in logs.

Recommended fix High confidence

Sophos UTM version 9.710

  1. Obtain the Sophos UTM version 9.710 upgrade package from the official Sophos download portal
  2. Back up the current Sophos UTM configuration before initiating the upgrade
  3. Apply the upgrade to Sophos UTM, upgrading to version 9.710 or later
  4. Verify the upgrade completed successfully by checking the version in the UTM administration interface
  5. Confirm the Mail Manager component is functioning properly after the upgrade

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

Fix this in Unified Threat Management Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
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,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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