dbcve.org
Command CentreApplication · Gallagher

CVE-2023-23570

HIGH · 8.1 CVSS v3.1 Published 2023-12-18
Fix available
A fix is available. Upgrade to 8.90.1620 or later.
See remediation →
87/100
Remediation priority · High
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
Client-Side enforcement of Server-Side security for the Command Centre server could be bypassed and lead to invalid configuration with undefined behavior. This issue affects: Gallagher Command Centre 8.90 prior to vEL8.90.1620 (MR2), all versions of 8.80 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

Client-side security controls in Gallagher Command Centre can be bypassed, allowing attackers to circumvent server-side security enforcement. This enables malicious input to reach the server that should have been blocked, leading to invalid configuration and undefined behavior.

MitigationApply vendor patch vEL8.90.1620 (MR2) or later to address server-side validation weaknesses and prevent client-side bypass exploitation.

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.80>= 8.90, < 8.90.1620

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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. Identify installed Gallagher Command Centre version
    Use system inventory tools, software registry, or Gallagher administrative interfaces to determine the currently installed version of Command Centre
    Affected if The installed version is <= 8.80 OR >= 8.90 but < 8.90.1620
  2. Verify client-side validation controls are active
    Review Gallagher Command Centre security configuration settings to confirm client-side input validation is enabled (this is typically the default state)
    Affected if Client-side validation controls are present in the configuration
  3. Confirm web interface exposure
    Examine network configuration to determine if the Command Centre web interface or API is accessible from external or untrusted networks
    Affected if The system is reachable from networks where untrusted users could send crafted requests

A system is affected if it runs Gallagher Command Centre version 8.80 or below, or version 8.90 through 8.90.1619, with client-side validation controls enabled and accessible to potential attackers.

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.90.1620 or later
Fixed in 8.90.1620
Interim mitigation

Apply vendor patch vEL8.90.1620 (MR2) or later to address server-side validation weaknesses and prevent client-side bypass exploitation.

Recommended fix High confidence

Gallagher Command Centre 8.90.1620 (MR2) or later

  1. 1. Identify the current installed version of Gallagher Command Centre by checking the server configuration or system information.
  2. 2. If running version 8.80 or earlier: Plan upgrade to version 8.90.1620 (MR2) or later.
  3. 3. If running version 8.90.x prior to 8.90.1620: Plan upgrade to version 8.90.1620 (MR2) or later.
  4. 4. Review release notes from security.gallagher.com for any upgrade prerequisites and migration requirements.
  5. 5. Perform a backup of the current Command Centre configuration and database.
  6. 6. Execute the upgrade to Gallagher Command Centre v8.90.1620 (MR2) or later following the official upgrade documentation.
  7. 7. Verify the installation and confirm the new version is running.
  8. 8. Test that the client-server security enforcement is functioning correctly after upgrade.
Caveat Review Gallagher release notes for 8.90.1620 for any configuration changes or migration requirements that may affect existing setups

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
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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