CVE-2019-19801
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 · uneditedIn Gallagher Command Centre Server versions of v8.10 prior to v8.10.1134(MR4), v8.00 prior to v8.00.1161(MR5), v7.90 prior to v7.90.991(MR5), v7.80 prior to v7.80.960(MR2) and v7.70 or earlier, an unprivileged but authenticated user is able to perform a backup of the Command Centre databases.
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 confidenceThis is an improper authorization vulnerability in Gallagher Command Centre where an authenticated but unprivileged user can access database backup functionality that should be restricted to administrators. This allows unauthorized backup of sensitive Command Centre databases.
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.70>= 7.80, < 7.80.960>= 7.90, < 7.90.991>= 8.00, < 8.00.1161>= 8.10, < 8.10.1134= 7.80.960= 7.90.991= 8.00.1161= 8.10.1134CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/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.
-
Determine installed Gallagher Command Centre versionCheck the product version through the Command Centre client (Help > About) or by inspecting the installation directory for a version file. Common locations include the program files folder or configuration files that contain version metadata.Affected if The installed version falls within any of these ranges: < 7.70, 7.80.x through 7.80.959, 7.90.x through 7.90.990, 8.00.x through 8.00.1160, or 8.10.x through 8.10.1133.
-
Identify user roles with backup accessReview Command Centre user roles and permissions through the Administration interface. Navigate to User Administration and examine which roles are assigned the Database Backup privilege or functionality.Affected if Any role other than Administrator roles has been granted database backup permissions.
-
Check for non-administrator usersIn Command Centre Administration, review all user accounts to identify those with authenticated access who hold roles other than Administrator.Affected if There exist authenticated users with non-Administrator roles.
-
Verify backup feature accessibilityLog in with a non-Administrator user account and attempt to access the database backup functionality (typically found in System > Maintenance or similar administrative sections).Affected if A non-Administrator authenticated user can access or initiate database backups.
If the installed version is affected (below the patched thresholds) AND there are non-Administrator users who can access the database backup feature, the environment is vulnerable to CVE-2019-19801.
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.707.80.9607.90.991
Upgrade Gallagher Command Centre to version v8.10.1134(MR4) or later, v8.00.1161(MR5) or later, v7.90.991(MR5) or later, or v7.80.960(MR2) or later to remediate this issue.
- Consultation2.0 h
- Implementation3.0 h
- Testing4.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-19801 — 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-19801 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