In Gallagher Command Centre v8.20 prior to v8.20.1093(MR2) it is possible to create Guard Tour events that when accessed via things like re…

published 2020-09-15 6y ago modified 2026-06-17 4mo ago also EUVD-2020-8065

cvss: 4.3; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.8%; EPSS 0.8% chance of exploitation in 30 days, percentile 56%
public exploits: 0; none known

In Gallagher Command Centre v8.20 prior to v8.20.1093(MR2) it is possible to create Guard Tour events that when accessed via things like reporting cause clients to temporarily hang or disconnect.

Patch / fix

fixed in 1

Gallagher Command Centre 8.20.1093(MR2)

Is CVE-2020-16099 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.80% chance of exploitation in the next 30 days, higher than 56% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
CNA	3.1	4.3	CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L
NVD	3.1	4.3	CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L
NVD	2.0	3.5	AV:N/AC:M/Au:S/C:N/I:N/A:P

Affected products

Gallagher Command Centre

Classification

Weakness

CWE-20 Improper Input Validation

References

security.gallagher.com /Security-Advisories/CVE-2020-16099
vendor-advisory

Sources

CVE List CVE-2020-16099
NVD CVE-2020-16099

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.