dbcve.org
Command CentreApplication · Gallagher

CVE-2023-22363

HIGH · 7.5 CVSS v3.1 Published 2023-07-25
Fix available
A fix is available. Upgrade to 8.80.1192 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
A stack-based buffer overflow in the Command Centre Server allows an attacker to cause a denial of service attack via assigning cardholders to an Access Group. This issue affects Command Centre: vEL8.80 prior to vEL8.80.1192 (MR2)

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

A stack-based buffer overflow vulnerability exists in Gallagher Command Centre Server when assigning cardholders to an Access Group. An attacker can exploit this by sending specially crafted requests during the cardholder-to-access-group assignment process, causing a denial of service. The vulnerability affects versions prior to vEL8.80.1192 (MR2) and carries a CVSS score of 7.5 (HIGH).

MitigationUpgrade Command Centre to version vEL8.80.1192 (MR2) or later to resolve the stack-based buffer overflow vulnerability.

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.80.1192

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 Gallagher Command Centre version
    Locate and inspect the installed Command Centre version through the system information panel, about dialog, or version check utility provided by Gallagher
    Affected if The installed version is 8.80 or higher but below 8.80.1192
  2. Confirm Access Group feature is active
    Check if the Access Group management module is enabled and accessible within the Command Centre administrative interface
    Affected if Access Group functionality is enabled and in use within the system
  3. Review cardholder assignment operations
    Audit recent access control logs or event records for cardholder-to-access-group assignment activities
    Affected if The system has processed any cardholder-to-access-group assignment requests
  4. Check for crash or instability indicators
    Examine system event logs, application logs, or crash dump files for stack overflow errors or unexpected service interruptions related to access group operations
    Affected if Stack-based buffer overflow symptoms or denial of service events are present in logs

A system is affected by this CVE if it runs Gallagher Command Centre version 8.80 through 8.80.1191 and utilizes the Access Group feature for cardholder assignments.

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.80.1192 or later
Fixed in 8.80.1192
Interim mitigation

Upgrade Command Centre to version vEL8.80.1192 (MR2) or later to resolve the stack-based buffer overflow vulnerability.

Recommended fix High confidence

vEL8.80.1192 (MR2) or later

  1. Identify the current Command Centre version by navigating to Help > About in the Command Centre client
  2. Schedule a maintenance window for the upgrade process
  3. Back up the Command Centre database and configuration files
  4. Download Command Centre vEL8.80.1192 (MR2) or later from the Gallagher download portal
  5. Follow the standard Command Centre upgrade procedure documented in the Gallagher installation guide
  6. After upgrade, verify the Command Centre server is running correctly
  7. Test that cardholder assignment to Access Groups functions without errors

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

Fix this in Command Centre Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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