dbcve.org
Improper Certificate ValidationWeakness · CWE-295

CVE-2024-41724

HIGH · 8.7 CVSS v3.1 Published 2025-03-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
96/100
Remediation priority · Urgent
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 (CWE-295) in the Gallagher Command Centre SALTO integration allowed an attacker to spoof the SALTO server. This issue affects all versions of Gallagher Command Centre prior to 9.20.1043.

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 Gallagher Command Centre SALTO integration performs improper certificate validation (CWE-295), failing to properly verify SSL/TLS certificates when communicating with the SALTO server. This allows an attacker to perform man-in-the-middle attacks and spoof the SALTO server, potentially intercepting or manipulating sensitive physical access control communications.

MitigationUpgrade Gallagher Command Centre to version 9.20.1043 or later to remediate the improper certificate validation vulnerability in the SALTO integration.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/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. Determine Gallagher Command Centre version
    Access the Command Centre administrative interface or check system information. Typically found in Help > About or system diagnostics. The version number is displayed as a set of four number groups (e.g., 9.10.1234).
    Affected if The installed version is lower than 9.20.1043.
  2. Identify if SALTO integration is configured
    Navigate to the Command Centre hardware or integration settings. Look for SALTO or third-party access control integrations in the configuration panels. Check the list of configured door controllers or integration modules.
    Affected if A SALTO integration module or connection is present and enabled in the system.
  3. Verify SALTO integration status
    In Command Centre, locate the SALTO server connection settings. Confirm whether the integration is actively communicating with a SALTO server by checking connection status or event logs for SALTO-related activity.
    Affected if The SALTO integration shows an active connection to a SALTO server.
  4. Check for man-in-the-middle exposure
    Review network traffic logs or SSL/TLS certificate validation logs if available. Determine whether the SALTO integration accepts certificates without proper chain validation or from untrusted CAs.
    Affected if The SALTO integration is configured to bypass certificate validation or uses insecure SSL/TLS settings.

A user is affected if their Gallagher Command Centre version is below 9.20.1043 and the SALTO integration module is enabled and configured to communicate with a SALTO server.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Gallagher Command Centre to version 9.20.1043 or later to remediate the improper certificate validation vulnerability in the SALTO integration.

Recommended fix High confidence

9.20.1043

  1. 1. Identify current Gallagher Command Centre version by accessing the Command Centre admin interface or checking system information.
  2. 2. Confirm the current version is earlier than 9.20.1043 to determine if the system is vulnerable.
  3. 3. Schedule a maintenance window for the upgrade process.
  4. 4. Back up the Command Centre database and configuration according to Gallagher documentation.
  5. 5. Obtain the Command Centre version 9.20.1043 or later from the official Gallagher download portal or through your Gallagher representative.
  6. 6. Apply the upgrade following the official Gallagher upgrade documentation, ensuring the SALTO integration components are updated.
  7. 7. After upgrade, verify the SALTO integration is functioning correctly and certificate validation is working as expected.
  8. 8. Confirm the new version number displays as 9.20.1043 or later in the admin interface.

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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