CVE-2019-12492
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 · uneditedGallagher Command Centre before 7.80.939, 7.90.x before 7.90.961, and 8.x before 8.00.1128 allows arbitrary event creation and information disclosure via the FT Command Centre Service and FT Controller Service services.
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 confidenceGallagher Command Centre before 7.80.939, 7.90.x before 7.90.961, and 8.x before 8.00.1128 contains a vulnerability in the FT Command Centre Service and FT Controller Service that allows arbitrary event creation and information disclosure, potentially enabling attackers to inject false security events or access sensitive system information.
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< 7.80.939>= 7.90.0, < 7.90.961>= 8.0, < 8.00.1128CVSS 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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N
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 versionLocate the Command Centre installation and retrieve its version number, typically found in the application properties, about screen, or installation directory documentation.Affected if The installed version is less than 7.80.939, or falls between 7.90.0 and 7.90.960 inclusive, or falls between 8.0 and 8.00.1127 inclusive.
-
Confirm FT Command Centre Service is activeCheck if the FT Command Centre Service is installed and running on the system. This is typically visible in Windows Services or can be queried via service management tools.Affected if The service is installed and running on a version that falls within the affected version ranges.
-
Confirm FT Controller Service is activeCheck if the FT Controller Service is installed and running on the system. This is typically visible in Windows Services or can be queried via service management tools.Affected if The service is installed and running on a version that falls within the affected version ranges.
-
Review FT service network exposureExamine firewall rules and network configuration to determine if the FT Command Centre Service and FT Controller Service are exposed to untrusted networks.Affected if Either FT service is accessible from untrusted networks on a version within the affected ranges.
You are affected if the installed Gallagher Command Centre version falls within any of the vulnerable ranges AND either the FT Command Centre Service or FT Controller Service is running and potentially exposed.
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 data7.80.9397.90.9618.00.1128
Upgrade Gallagher Command Centre to version 7.80.939, 7.90.961, or 8.00.1128 or later. If immediate patching is not possible, restrict network access to the FT services and monitor for unauthorized event creation.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-12492 — 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-2019-12492 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