CVE-2020-25223
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 · uneditedA remote code execution vulnerability exists in the WebAdmin of Sophos SG UTM before v9.705 MR5, v9.607 MR7, and v9.511 MR11
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 confidenceRemote code execution vulnerability in the WebAdmin interface of Sophos SG UTM (Unified Threat Management) appliances. The vulnerability affects older software versions before v9.705 MR5, v9.607 MR7, and v9.511 MR11, allowing unauthenticated attackers to execute arbitrary code via the web administration interface.
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< 9.511>= 9.600, < 9.607>= 9.700, < 9.705= 9.511= 9.607= 9.705CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Check Sophos UTM firmware versionLog into the WebAdmin interface and navigate to System > About, or run 'version' via SSH on the applianceAffected if The version shown is less than 9.511, or between 9.600-9.606, or between 9.700-9.704 (including 9.511, 9.607, 9.705)
-
Verify WebAdmin network exposureCheck if TCP port 4444 (default WebAdmin port) is accessible from untrusted network interfaces using a port scanner or by reviewing firewall rulesAffected if The WebAdmin interface is reachable from any network other than a trusted admin network or VPN
-
Confirm WebAdmin service statusRun 'fwctl --port' or check the service configuration to confirm WebAdmin is enabled and listeningAffected if WebAdmin is enabled and listening on a network-facing interface
You are affected if the Sophos UTM firmware version falls within the vulnerable ranges AND the WebAdmin interface is accessible from untrusted networks.
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 · scoped9.5119.6079.705
Upgrade Sophos SG UTM to patched versions (v9.705 MR5, v9.607 MR7, v9.511 MR11 or later). If immediate patching is not possible, restrict network access to the WebAdmin interface using firewall rules or VPN access.
Upgrade to v9.705 MR5 (for 9.7xx branch), v9.607 MR7 (for 9.6xx branch), or v9.511 MR11 (for 9.5xx branch)
- 1. Identify the current version of Sophos SG UTM by checking the WebAdmin dashboard or running 'version' command in shell
- 2. Determine which version branch you are on (9.511, 9.607, or 9.700 series)
- 3. For systems on 9.511 branch: upgrade to version 9.511 MR11 or later
- 4. For systems on 9.607 branch: upgrade to version 9.607 MR7 or later
- 5. For systems on 9.700 branch: upgrade to version 9.705 MR5 or later
- 6. Download the appropriate upgrade image from Sophos support portal
- 7. Apply the upgrade via WebAdmin or via shell using 'upsysupdate' command
- 8. Verify the upgrade completed successfully and WebAdmin is accessible
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.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 $2,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-25223 — 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-2020-25223 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