dbcve.org
Command CentreApplication · Gallagher

CVE-2023-23568

MEDIUM · 5.4 CVSS v3.1 Published 2023-07-25
Fix available
A fix is available. Upgrade to 8.50.2831 / 8.60.2347 or later.
See remediation →
60/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
Improper privilege validation in Command Centre Server allows authenticated unprivileged operators to modify and view Personal Data Fields. This issue affects Command Centre: vEL 8.90 prior to vEL8.90.1318 (MR1), vEL8.80 prior to vEL8.80.1192 (MR2), vEL8.70 prior to vEL8.70.2185 (MR4), vEL8.60 prior to vEL8.60.2347 (MR6), vEL8.50 prior to vEL8.50.2831 (MR8), all versions vEL8.40 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

Command Centre Server contains improper privilege validation that allows authenticated users with unprivileged operator roles to modify and view Personal Data Fields that should be restricted to higher-privilege users. The vulnerability stems from insufficient authorization checks in the server's access control logic.

MitigationUpgrade Command Centre to one of the patched versions: vEL8.90.1318 (MR1), vEL8.80.1192 (MR2), vEL8.70.2185 (MR4), vEL8.60.2347 (MR6), or vEL8.50.2831 (MR8).

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.40.2216>= 8.50, < 8.50.2831>= 8.60, < 8.60.2347>= 8.70, < 8.70.2185>= 8.80, < 8.80.1192>= 8.90, < 8.90.1318

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/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
    Locate the Command Centre Server version information in the system administration interface or about dialog, typically found in the server management console or registry/configuration files
    Affected if The installed version falls within any of these ranges: <= 8.40.2216; >= 8.50, < 8.50.2831; >= 8.60, < 8.60.2347; >= 8.70, < 8.70.2185; >= 8.80, < 8.80.1192; >= 8.90, < 8.90.1318
  2. Verify Personal Data Fields are configured
    Inspect the Command Centre configuration for any defined Personal Data Fields, which are used to store sensitive personal information tied to cardholders or operators
    Affected if Personal Data Fields are defined in the system configuration and are accessible through the operator interface
  3. Confirm presence of unprivileged operator accounts
    Review the operator accounts defined in Command Centre and identify those assigned to unprivileged operator roles (non-adminstrator roles)
    Affected if There exist operator accounts with operator-level privileges who should not have access to restricted Personal Data Fields
  4. Review access logs for Personal Data Field access
    Examine Command Centre audit logs or access records for any operations involving Personal Data Fields performed by operators with unprivileged roles
    Affected if Unprivileged operators have viewed or modified Personal Data Fields that should be restricted to higher-privilege users

You are affected if your Command Centre version is within the affected ranges AND unprivileged operators have accessed Personal Data Fields that should be restricted to higher-privilege users.

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.50.2831 / 8.60.2347 / 8.70.2185 or later
Fixed in 8.50.28318.60.23478.70.2185
Interim mitigation

Upgrade Command Centre to one of the patched versions: vEL8.90.1318 (MR1), vEL8.80.1192 (MR2), vEL8.70.2185 (MR4), vEL8.60.2347 (MR6), or vEL8.50.2831 (MR8).

Recommended fix High confidence

Upgrade to the minimum fixed version for your branch: 8.50.2831+, 8.60.2347+, 8.70.2185+, 8.80.1192+, or 8.90.1318+ (or latest available)

  1. 1. Identify the currently installed Command Centre version by checking the Server interface or system information
  2. 2. Based on the current version branch, upgrade to the minimum fixed version: For 8.40.x and prior, upgrade to 8.50.2831 or later; For 8.50.x, upgrade to 8.50.2831 (MR8) or later; For 8.60.x, upgrade to 8.60.2347 (MR6) or later; For 8.70.x, upgrade to 8.70.2185 (MR4) or later; For 8.80.x, upgrade to 8.80.1192 (MR2) or later; For 8.90.x, upgrade to 8.90.1318 (MR1) or later
  3. 3. Verify the upgrade was successful by confirming the new version in Command Centre
  4. 4. Test that unprivileged operators can no longer modify or view Personal Data Fields beyond their authorized access
Caveat Review release notes for your specific version branch for any compatibility notes or changes to operator role permissions

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

Fix this in Command Centre Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,780
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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