CVE-2021-23204
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 · uneditedExposure of Sensitive Information to an Unauthorized Actor vulnerability in Gallagher Command Centre Server allows OSDP key material to be exposed to Command Centre Operators. This issue affects: Gallagher Command Centre 8.40 versions prior to 8.40.1888 (MR3); 8.30 versions prior to 8.30.1359 (MR3).
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 confidenceOSDP (Open Supervised Device Protocol) key material is improperly exposed to unauthorized Command Centre Operators in Gallagher Command Centre Server. This is an information disclosure vulnerability where sensitive cryptographic keys used for access control device communication are visible to operators who should not have access to them.
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>= 8.30, < 8.30.1359>= 8.40, < 8.40.1888CVSS 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
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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 checksWork through these to decide whether this CVE applies to you.
-
Verify Gallagher Command Centre installationLocate the Gallagher Command Centre application on the systemAffected if Gallagher Command Centre is not installed - the CVE does not apply
-
Check installed Command Centre versionDetermine the version of Gallagher Command Centre (typically via application About dialog, system information, or installed programs list)Affected if Version is 8.30.0 or higher but below 8.30.1359, OR 8.40.0 or higher but below 8.40.1888 - these are the vulnerable version ranges
-
Confirm OSDP is configuredDetermine whether OSDP (Open Supervised Device Protocol) is enabled or configured within the Command Centre installationAffected if OSDP is not configured in the environment - the vulnerability requires OSDP to be in use for the exposure to occur
-
Review operator access to OSDP key materialInspect operator role permissions to verify whether operators can view OSDP cryptographic keys that they should not have access toAffected if Operators without appropriate privileges can view OSDP keys - this confirms the vulnerability is present
Environment is affected if running a vulnerable version of Gallagher Command Centre (8.30.0-8.30.1358 or 8.40.0-8.40.1887) with OSDP configured and unauthorized operators can access sensitive cryptographic key material.
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.
From vendor data8.30.13598.40.1888
Upgrade Gallagher Command Centre to version 8.40.1888 (MR3) or later for 8.40.x, or version 8.30.1359 (MR3) or later for 8.30.x. OSDP keys are sensitive security credentials and should be rotated after patching.
- Consultation2.0 h
- Implementation3.0 h
- Testing5.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,280.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-23204 — 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-23204 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