CVE-2020-16100
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 · uneditedIt is possible for an unauthenticated remote DCOM websocket connection to crash the Command Centre service's DCOM websocket thread due to improper shutdown of closed websocket connections, preventing it from accepting future DCOM websocket (Configuration Client) connections. Affected versions are v8.20 prior to v8.20.1166(MR3), v8.10 prior to v8.10.1211(MR5), v8.00 prior to v8.00.1228(MR6), all versions of 7.90 and earlier.
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 confidenceAn unauthenticated remote attacker can crash the Command Centre service's DCOM websocket thread by sending malformed websocket connections that are not properly shut down, causing a denial of service where the service cannot accept future Configuration Client connections.
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>= 8.00, < 8.00.1228>= 8.10, < 8.10.1211>= 8.20, < 8.20.1166= 8.00.1228= 8.10.1211= 8.20.1166CVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 installed Gallagher Command Centre versionCheck the Command Centre service version through the Configuration Client or via the Windows Services panel for the 'Gallagher Command Centre' service propertiesAffected if The installed version is lower than 8.00.1228, 8.10.1211, or 8.20.1166 (or matches exactly one of these three versions if those are considered vulnerable)
-
Verify DCOM websocket functionality is enabledConfirm the DCOM interface is active by checking if Configuration Client connections are accepted and the websocket listener is running on the serverAffected if The DCOM websocket thread is exposed and accepting connections (default behavior for Command Centre)
-
Check for service availability issuesAttempt a Configuration Client connection to the server or review Windows Event Logs for recent Command Centre service crashes or connection failuresAffected if The service has crashed due to malformed websocket connections or is unable to accept Configuration Client connections
-
Review Windows Event Logs for crash eventsOpen Windows Event Viewer, navigate to Application logs, and look for Event ID entries or error messages related to Command Centre DCOM or websocket thread failures around the time of the vulnerabilityAffected if Recent event log entries show DCOM websocket thread crashes or denial of service events
A system is affected if it is running any version of Gallagher Command Centre from 8.00 through the versions just before the patched releases (8.00.1228, 8.10.1211, 8.20.1166), with the DCOM websocket interface exposed, and experiencing or susceptible to service crashes from malformed websocket connections
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.
From vendor data8.00.12288.10.12118.20.1166
Upgrade to patched versions v8.20.1166(MR3) or later, v8.10.1211(MR5) or later, or v8.00.1228(MR6) or later. For systems on 7.90 and earlier, contact the vendor for patch availability.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-16100 — 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-16100 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