CVE-2020-15069
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 · uneditedSophos XG Firewall 17.x through v17.5 MR12 allows a Buffer Overflow and remote code execution via the HTTP/S Bookmarks feature for clientless access. Hotfix HF062020.1 was published for all firewalls running v17.x.
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 confidenceA buffer overflow vulnerability exists in the HTTP/S Bookmarks feature of Sophos XG Firewall versions 17.x through v17.5 MR12, allowing remote attackers to execute arbitrary code on the affected firewall 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>= 17.0, < 17.5= 17.5CVSS 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.
-
Identify the Sophos XG Firewall firmware versionAccess the firewall admin console or run 'version' command in CLI to retrieve the installed firmware version numberAffected if The firmware version is 17.x or specifically 17.5 (any MR variant)
-
Confirm the exact version numberCompare the installed firmware version against the affected range: versions >= 17.0 and < 17.5, or exactly version 17.5Affected if The installed version falls within 17.0 to 17.4.x inclusive, or equals 17.5 (any MR release)
-
Determine if HTTP/S Bookmarks feature is configuredCheck the firewall web admin interface under the HTTP/S Bookmarks settings, or inspect the firewall configuration for bookmark entriesAffected if HTTP/S Bookmarks are actively configured and the firewall is processing bookmark-related traffic
The environment is affected if the Sophos XG Firewall is running firmware version 17.x through v17.5 MR12 AND the HTTP/S Bookmarks feature is enabled with active bookmark configurations.
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 · scoped17.5
Apply hotfix HF062020.1 to all Sophos XG Firewall devices running v17.x to remediate this vulnerability.
Upgrade to Sophos XG Firewall v17.5 MR12 or later, or apply Hotfix HF062020.1
- 1. Identify the current Sophos XG Firewall firmware version via the management console or command line.
- 2. If running version 17.0 through 17.5 MR12 (or any v17.x version), apply Hotfix HF062020.1 which addresses this buffer overflow vulnerability in the HTTP/S Bookmarks feature.
- 3. Alternatively, upgrade the firmware to version 17.5 MR12 or later which contains the fix.
- 4. After applying the hotfix or upgrade, verify the fix was successfully applied by checking the firmware version and hotfix status.
- 5. Confirm the HTTP/S Bookmarks feature is functioning correctly after the update.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-15069 — 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-15069 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