dbcve.org
Command CentreApplication · Gallagher

CVE-2024-21815

MEDIUM · 6.5 CVSS v3.1 Published 2024-03-05
Fix available
A fix is available. Upgrade to 8.70.2526 / 8.80.1526 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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
Insufficiently protected credentials (CWE-522) for third party DVR integrations to the Command Centre Server are accessible to authenticated but unprivileged users. This issue affects: Gallagher Command Centre 9.00 prior to vEL9.00.1774 (MR2), 8.90 prior to vEL8.90.1751 (MR3), 8.80 prior to vEL8.80.1526 (MR4), 8.70 prior to vEL8.70.2526 (MR6),  all version of 8.60 and prior.

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

This is a credential exposure vulnerability (CWE-522) in Gallagher Command Centre where third-party DVR integration credentials are stored with insufficient protection, allowing authenticated but unprivileged users to access sensitive authentication material for connected DVR systems.

MitigationUpgrade Gallagher Command Centre to the specified patched versions (vEL9.00.1774, vEL8.90.1751, vEL8.80.1526, or vEL8.70.2526 depending on your current branch). This is a MEDIUM severity issue requiring authenticated access, so prioritize upgrading systems with untrusted user populations.

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.60>= 8.70, < 8.70.2526>= 8.80, < 8.80.1526>= 8.90, < 8.90.1751>= 9.00, < 9.00.1774

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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. Determine installed Gallagher Command Centre version
    Access the Command Centre admin interface and navigate to Help > About, or check the installation directory for version information files. Alternatively, query the system via the admin console for the exact build version.
    Affected if The installed version is <= 8.60, OR >= 8.70 and < 8.70.2526, OR >= 8.80 and < 8.80.1526, OR >= 8.90 and < 8.90.1751, OR >= 9.00 and < 9.00.1774
  2. Verify third-party DVR integration is configured
    Log into the Command Centre admin interface and navigate to the Integrations or Hardware configuration section. Look for any configured third-party DVR/NVR integrations. Check if any DVR systems from manufacturers such as Hikvision, Axis, Bosch, or similar are connected.
    Affected if DVR integration with third-party systems is enabled and configured in Command Centre
  3. Review user access controls for integration settings
    In the Command Centre admin interface, navigate to Users and Roles or Access Control settings. Identify whether users with limited or basic privileges (non-administrators) have any access to view or modify integration configurations, including DVR connection settings.
    Affected if Non-administrative users have any level of access to view integration or DVR configuration screens

You are affected if your Command Centre version falls within any of the vulnerable ranges AND you have third-party DVR integrations configured AND unprivileged users can access integration settings.

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.70.2526 / 8.80.1526 / 8.90.1751 or later
Fixed in 8.70.25268.80.15268.90.1751
Interim mitigation

Upgrade Gallagher Command Centre to the specified patched versions (vEL9.00.1774, vEL8.90.1751, vEL8.80.1526, or vEL8.70.2526 depending on your current branch). This is a MEDIUM severity issue requiring authenticated access, so prioritize upgrading systems with untrusted user populations.

Recommended fix High confidence

Gallagher Command Centre vEL8.70.2526+, vEL8.80.1526+, vEL8.90.1751+, or vEL9.00.1774+ (depending on major version branch)

  1. Identify the current installed version of Gallagher Command Centre
  2. If running version 8.60 or prior, plan upgrade to a supported version (8.70.2526+, 8.80.1526+, 8.90.1751+, or 9.00.1774+) as 8.60 and earlier have no fix
  3. If running version 8.70.x, upgrade to vEL8.70.2526 (MR6) or later
  4. If running version 8.80.x, upgrade to vEL8.80.1526 (MR4) or later
  5. If running version 8.90.x, upgrade to vEL8.90.1751 (MR3) or later
  6. If running version 9.00.x, upgrade to vEL9.00.1774 (MR2) or later
  7. After upgrade, verify that the third-party DVR integration credentials are no longer accessible to unprivileged users
  8. Review user permissions to ensure only privileged users have access to credential storage areas
Caveat Review release notes for the target version for any breaking changes or migration requirements before upgrading

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

Fix this in Command Centre Scoped from the published advisory
  • Consultation6.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,840
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,144.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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