CVE-2023-1671
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 pre-auth command injection vulnerability in the warn-proceed handler of Sophos Web Appliance older than version 4.3.10.4 allows execution of arbitrary code.
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 confidenceA pre-authentication command injection vulnerability exists in the warn-proceed handler of Sophos Web Appliance versions prior to 4.3.10.4. An attacker can inject arbitrary commands through this web interface handler without any authentication, leading to complete remote code execution on the affected appliance.
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< 4.3.10.4CVSS 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.
-
Confirm Sophos Web Appliance is installedIdentify the appliance by accessing the web management interface or checking system hostname/DNS entries that resolve to the device. The appliance typically exposes a web console on ports 443 or 80.Affected if The target system is a Sophos Web Appliance.
-
Determine the installed versionLog into the web admin interface and navigate to the About or System Information page, or check the version via CLI if accessible (e.g., cat /etc/version or similar system files). Compare the version number to 4.3.10.4.Affected if The installed version is lower than 4.3.10.4.
-
Verify warn-proceed handler accessibilityAttempt to access the warn-proceed endpoint via HTTP/HTTPS. This is typically a web handler used during certain workflows. Try accessing common paths or use reconnaissance to identify the endpoint.Affected if The warn-proceed handler is reachable without authentication.
-
Check network exposureDetermine if the appliance management interface is directly accessible from untrusted networks (such as the public internet) by reviewing firewall rules, NAT configurations, or performing an external port scan of the appliance IP.Affected if The web interface is exposed to unauthenticated/untrusted network access without VPN or IP restrictions.
A user is affected if they are running Sophos Web Appliance version lower than 4.3.10.4 with the warn-proceed handler accessible to unauthenticated attackers on their network.
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 · scoped4.3.10.4
Upgrade Sophos Web Appliance to version 4.3.10.4 or later. If immediate patching is not possible, consider restricting network access to the appliance's management interface via firewall rules or VPN until the patch can be applied.
4.3.10.4 or later
- 1. Identify current Sophos Web Appliance version via web interface or CLI
- 2. Navigate to Sophos support portal and download version 4.3.10.4 or later
- 3. Follow Sophos official upgrade documentation to apply the patch
- 4. Verify upgrade was successful by checking the new version number
- 5. Confirm the warn-proceed handler is no longer accessible without authentication
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,392.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-1671 — 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-2023-1671 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