CVE-2021-23162
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 · uneditedImproper validation of the cloud certificate chain in Mobile Connect allows man-in-the-middle attack to impersonate the legitimate Command Centre Server. This issue affects: Gallagher Command Centre Mobile Connect for Android 15 versions prior to 15.04.040; version 14 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 confidenceThe Gallagher Command Centre Mobile Connect Android application fails to properly validate the SSL/TLS certificate chain when establishing connections to the Command Centre Server. This allows an attacker positioned on the network to perform a man-in-the-middle attack, intercepting and potentially modifying communications between the mobile app and the server by presenting a fraudulent certificate that the app accepts without proper chain-of-trust verification.
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<= 14.0>= 15.0, < 15.04.040CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/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 checksWork through these to decide whether this CVE applies to you.
-
Locate the Gallagher Command Centre Mobile Connect appOn the Android device, go to Settings > Apps and search for 'Mobile Connect' or 'Gallagher', or check the app drawer for the app iconAffected if The app is not found on the device, the user is not affected by this vulnerability in this specific app
-
Identify the installed app versionIn Settings > Apps > Mobile Connect (or Gallagher Command Centre Mobile Connect), tap on 'App info' or 'App details' to view the version number and build numberAffected if Version information cannot be retrieved or is missing, further investigation may be needed
-
Compare the installed version against affected rangesCompare the displayed version number to the affected ranges: version 14.0 and below, OR version 15.0 through 15.04.039 inclusive. Note the exact version number shown (for example, 14.0, 15.0, 15.04.038, etc.)Affected if The installed version is 14.0 or lower, OR the installed version is 15.0 through 15.04.039 (any version below 15.04.040)
-
Verify the vulnerability is exploitable in your environmentThis vulnerability requires the mobile app to connect to a Command Centre Server over a network where an attacker could intercept traffic. Consider whether the app is used on untrusted networks (public WiFi, etc.)Affected if The app connects to Command Centre Server on networks where third parties could intercept traffic (MITM attack vector exists)
A user is affected if Gallagher Command Centre Mobile Connect for Android is installed with version 14.0 or below, or version 15.0 through 15.04.039, and connects to the server over potentially untrusted networks.
Generated from the published advisory. Verify against your own configuration.
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 · scoped15.04.040
Upgrade Gallagher Command Centre Mobile Connect for Android to version 15.04.040 or later, which contains proper certificate chain validation. Until then, avoid using mobile connect on untrusted networks.
15.04.040
- Upgrade Gallagher Command Centre Mobile Connect for Android to version 15.04.040 or later
- Verify the upgrade was successful by checking the application version in the app settings
- Consult Gallagher release notes for any additional configuration requirements post-upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-23162 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-23162 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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