dbcve.org
Command CentreApplication · Gallagher

CVE-2021-23167

MEDIUM · 6.8 CVSS v3.1 Published 2021-11-18
Fix available
A fix is available. Upgrade to 8.30.1454 / 8.40.2063 or later.
See remediation →
77/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
Improper certificate validation vulnerability in SMTP Client allows man-in-the-middle attack to retrieve sensitive information from the Command Centre Server. This issue affects: Gallagher Command Centre 8.50 versions prior to 8.50.2048 (MR3); 8.40 versions prior to 8.40.2063 (MR4); 8.30 versions prior to 8.30.1454 (MR4) ; version 8.20 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 SMTP Client in Gallagher Command Centre does not properly validate SSL/TLS certificates, allowing an attacker positioned between the client and server to intercept communications and retrieve sensitive information by presenting a fraudulent certificate.

MitigationUpgrade to Gallagher Command Centre version 8.50.2048 (MR3), 8.40.2063 (MR4), or 8.30.1454 (MR4) or later to obtain the patched SMTP client with proper certificate validation.

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.20>= 8.30, < 8.30.1454>= 8.40, < 8.40.2063>= 8.50, < 8.50.2048

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

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/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. Confirm SMTP client is in use
    Review Command Centre configuration to determine if the SMTP client feature is enabled for email notifications, alerts, or integration with external systems
    Affected if SMTP client is configured and actively used to send email from Command Centre
  2. Identify installed Command Centre version
    Access the Command Centre admin interface or check system information to find the exact version number of the installed Gallagher Command Centre software
    Affected if The installed version falls within any of these ranges: <= 8.20, >= 8.30 but < 8.30.1454, >= 8.40 but < 8.40.2063, or >= 8.50 but < 8.50.2048
  3. Check SMTP SSL/TLS certificate validation setting
    Examine the SMTP client configuration in Command Centre to determine whether SSL/TLS certificate validation is properly enforced or if it is bypassed
    Affected if Certificate validation is disabled, not enforced, or set to accept any valid certificate without proper chain verification

A user is affected if they use the SMTP client feature in any Command Centre version listed as vulnerable, particularly when SSL/TLS encryption is enabled but certificate validation is not properly configured.

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.30.1454 / 8.40.2063 / 8.50.2048 or later
Fixed in 8.30.14548.40.20638.50.2048
Interim mitigation

Upgrade to Gallagher Command Centre version 8.50.2048 (MR3), 8.40.2063 (MR4), or 8.30.1454 (MR4) or later to obtain the patched SMTP client with proper certificate validation.

Recommended fix High confidence

Upgrade to 8.50.2048 (MR3) for 8.50 branch, 8.40.2063 (MR4) for 8.40 branch, or 8.30.1454 (MR4) for 8.30 branch. 8.20 and earlier should upgrade to at least 8.30.1454+

  1. 1. Identify the current Gallagher Command Centre version by checking the system information or release notes
  2. 2. Determine which version branch you are currently on (8.20, 8.30, 8.40, or 8.50)
  3. 3. Plan upgrade to the minimum fixed version for your branch: 8.20 users should upgrade to 8.30.1454 or later; 8.30 users should upgrade to 8.30.1454 (MR4) or later; 8.40 users should upgrade to 8.40.2063 (MR4) or later; 8.50 users should upgrade to 8.50.2048 (MR3) or later
  4. 4. Review release notes for the target version to understand new features and changes
  5. 5. Backup the Command Centre configuration and database before upgrading
  6. 6. Test the upgrade in a non-production environment first
  7. 7. Perform the upgrade during a planned maintenance window
  8. 8. After upgrade, verify SMTP client functionality and test TLS/SSL certificate validation is working correctly
Caveat Review release notes for your specific version upgrade as there may be feature changes and configuration adjustments between major version branches

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
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
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,808.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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