First published: Tue Sep 15 2020(Updated: )
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.
Credit: disclosures@gallagher.com
Affected Software | Affected Version | How to fix |
---|---|---|
Gallagher Command Centre | >=8.00<8.00.1228 | |
Gallagher Command Centre | >=8.10<8.10.1211 | |
Gallagher Command Centre | >=8.20<8.20.1166 | |
Gallagher Command Centre | =8.00.1228 | |
Gallagher Command Centre | =8.10.1211 | |
Gallagher Command Centre | =8.20.1166 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2020-16100 has been classified with a severity that indicates it could lead to Denial of Service due to remote daemon disruptions.
To mitigate CVE-2020-16100, you should upgrade to the latest version of Gallagher Command Centre beyond the affected versions.
CVE-2020-16100 affects versions of Gallagher Command Centre from 8.00 to 8.20, including specific versions 8.00.1228, 8.10.1211, and 8.20.1166.
Yes, CVE-2020-16100 can be exploited remotely through unauthenticated DCOM websocket connections.
CVE-2020-16100 can cause the Command Centre service to crash, preventing it from accepting future DCOM websocket connections.