dbcve.org
Command CentreApplication · Gallagher

CVE-2019-15294

CRITICAL · 9.8 CVSS v3.0 Published 2019-08-28
Fix available
A fix is available. Upgrade to 8.10.1092 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
An issue was discovered in Gallagher Command Centre 8.10 before 8.10.1092(MR2). Upon an upgrade, if a custom service account is in use and the visitor management service is installed, the Windows username and password for this service are logged in cleartext to the Command_centre.log file.

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 confidence

During an upgrade of Gallagher Command Centre 8.10 (prior to 8.10.1092 MR2), if a custom service account is configured and the visitor management service is installed, the Windows username and password for this service account are written in cleartext to the Command_centre.log file, exposing credentials.

MitigationUpgrade to Gallagher Command Centre 8.10.1092(MR2) or later. Additionally, audit and rotate any credentials that may have been exposed in logs, and review log files for evidence of compromise.

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
Command CentreApplication
Affected:>= 8.10, < 8.10.1092

CVSS 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
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Command Centre version
    Locate the Gallagher Command Centre installation and retrieve the version number. This is typically found in the program files directory, in registry, or via the application itself under Help > About.
    Affected if The installed version is 8.10 or higher but lower than 8.10.1092 (such as 8.10.1091, 8.10.1080, 8.10.1000, etc.)
  2. Verify visitor management service is installed
    Check if the Gallagher Visitor Management service is present on the system. This can be done via Windows Services (services.msc) looking for a service related to Visitor Management, or via Gallagher configuration tools.
    Affected if The visitor management service is installed and enabled on the system
  3. Confirm custom service account configuration
    Review the Gallagher Command Centre configuration to determine if a custom Windows service account (rather than a default account) is configured for running the services.
    Affected if A custom service account is configured for Command Centre services
  4. Inspect log file for exposed credentials
    Open the Command_centre.log file (typically found in the Command Centre logs directory) and search for patterns matching Windows usernames and passwords in cleartext. Look for strings containing 'username' or 'password' fields or similar credential-like data.
    Affected if Cleartext Windows usernames and passwords are present in the Command_centre.log file, particularly entries that appear during or after an upgrade operation

A system is affected if it runs Gallagher Command Centre version 8.10 through 8.10.1091, has the visitor management service installed, uses a custom service account, and contains cleartext credentials in the Command_centre.log file.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 8.10.1092 or later
Fixed in 8.10.1092
Interim mitigation

Upgrade to Gallagher Command Centre 8.10.1092(MR2) or later. Additionally, audit and rotate any credentials that may have been exposed in logs, and review log files for evidence of compromise.

Recommended fix High confidence

Command Centre 8.10.1092 (MR2) or later

  1. 1. Ensure you have a complete backup of your Command Centre system and configuration before proceeding with any upgrade.
  2. 2. Download Gallagher Command Centre version 8.10.1092 (MR2) or later from the official Gallagher download portal.
  3. 3. Schedule a maintenance window as upgrades may require downtime.
  4. 4. Stop all Command Centre services before initiating the upgrade.
  5. 5. Run the Command Centre installer and follow the upgrade wizard instructions.
  6. 6. After upgrade completes, verify the Command_centre.log file no longer contains cleartext passwords.
  7. 7. Consider rotating the service account credentials as a precautionary measure since they may have been exposed in logs.
Caveat Review Gallagher release notes for any configuration or behavioral changes between your current version and 8.10.1092

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Command Centre Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-15294 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-15294 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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