dbcve.org
Command CentreApplication · Gallagher

CVE-2021-23146

HIGH · 7.5 CVSS v3.1 Published 2021-11-18
Fix available
A fix is available. Upgrade to 8.10.1284 / 8.20.1259 or later.
See remediation →
84/100
Remediation priority · High
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 Incomplete Comparison with Missing Factors vulnerability in the Gallagher Controller allows an attacker to bypass PIV verification. This issue affects: Gallagher Command Centre 8.40 versions prior to 8.40.1888 (MR3); 8.30 versions prior to 8.30.1359 (MR3); 8.20 versions prior to 8.20.1259 (MR5); 8.10 versions prior to 8.10.1284 (MR7); version 8.00 and prior versions.

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

The vulnerability is an incomplete comparison flaw in the Gallagher Command Centre's PIV (Personal Identity Verification) credential verification logic. The system fails to properly validate all required authentication factors when verifying PIV credentials, allowing an attacker to bypass the verification process and potentially gain unauthorized physical access through the access control system.

MitigationApply the appropriate patch version for your Command Centre branch: upgrade to 8.40.1888 (MR3), 8.30.1359 (MR3), 8.20.1259 (MR5), 8.10.1284 (MR7), or later versions. For older branches, migrate to a supported version.

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.00>= 8.10, < 8.10.1284>= 8.20, < 8.20.1259>= 8.30, < 8.30.1359>= 8.40, < 8.40.1888

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

CVSS:3.1/AV:N/AC:L/PR:N/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 checks

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

  1. Identify installed Command Centre version
    Access the Gallagher Command Centre admin interface and navigate to Help > About, or check the installation logs and system information panel to locate the exact version number (e.g., 8.30.1200)
    Affected if The installed version falls within any of these ranges: <= 8.00, >= 8.10 and < 8.10.1284, >= 8.20 and < 8.20.1259, >= 8.30 and < 8.30.1359, or >= 8.40 and < 8.40.1888
  2. Confirm PIV credential verification is configured
    In the Command Centre admin interface, navigate to Access Control > Credentials > PIV Credentials, or check the credential provider configuration to determine if PIV credential verification is enabled for any doors or access points
    Affected if PIV credential verification is actively configured and used for access control
  3. Verify PIV authentication factor settings
    Review the PIV credential reader configuration and authentication policy settings to confirm that the system is validating PIV credentials without the complete factor comparison (specific configuration details may vary by deployment)
    Affected if PIV credential verification is enabled and the version is in the affected range, the incomplete comparison flaw may be present

A user is affected if their Command Centre version is less than 8.10.1284, 8.20.1259, 8.30.1359, or 8.40.1888 AND they have PIV credential verification configured in their access control system.

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.1284 / 8.20.1259 / 8.30.1359 or later
Fixed in 8.10.12848.20.12598.30.1359
Interim mitigation

Apply the appropriate patch version for your Command Centre branch: upgrade to 8.40.1888 (MR3), 8.30.1359 (MR3), 8.20.1259 (MR5), 8.10.1284 (MR7), or later versions. For older branches, migrate to a supported version.

Recommended fix High confidence

8.40.1888 (MR3), 8.30.1359 (MR3), 8.20.1259 (MR5), or 8.10.1284 (MR7) depending on your version branch

  1. Identify the currently installed Gallagher Command Centre version by checking the controller or admin interface
  2. Determine which version branch you are running (8.00, 8.10, 8.20, 8.30, or 8.40)
  3. For Command Centre 8.40: upgrade to version 8.40.1888 (MR3) or later
  4. For Command Centre 8.30: upgrade to version 8.30.1359 (MR3) or later
  5. For Command Centre 8.20: upgrade to version 8.20.1259 (MR5) or later
  6. For Command Centre 8.10: upgrade to version 8.10.1284 (MR7) or later
  7. For Command Centre 8.00 or prior: upgrade to at least version 8.10.1284 or later (recommended to upgrade to latest stable branch)
  8. After upgrade, verify PIV authentication is functioning correctly
Caveat Standard upgrade considerations apply - review release notes for your specific version path for any configuration or compatibility notes

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

Fix this in Command Centre Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get the upgrade done

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

Check whether your project pulls in CVE-2021-23146 — 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-2021-23146 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