dbcve.org
Sensitive Information in LogsWeakness · CWE-532

CVE-2024-42407

HIGH · 8.5 CVSS v3.1 Published 2024-12-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
91/100
Remediation priority · Urgent
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
Insertion of Sensitive Information into Log File (CWE-532) in the Gallagher Command Centre Alarm Transmitter feature could allow an authenticated Operator to view some security sensitive information to which they have not been granted access. This issue affects: Command Centre Server 9.10 prior to 9.10.2149 (MR4), 9.00 prior to 9.00.2374 (MR5), 8.90 prior to 8.90.2356 (MR6), all versions of 8.80 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

The Alarm Transmitter feature in Gallagher Command Centre Server writes security-sensitive information to log files that authenticated Operators can access, violating access control boundaries. An operator with limited permissions can view sensitive data they should not have permission to see through these logs.

MitigationApply the vendor-supplied patch (9.10.2149, 9.00.2374, or 8.90.2356 depending on branch) to remediate the improper logging of sensitive information in the Alarm Transmitter feature.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/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 Command Centre installation and version
    Locate the Gallagher Command Centre installation and determine the installed version number. This is typically found in Windows Programs and Features, or via the Command Centre server configuration. The version format appears as 9.x.xxxx or 8.90.xxxx
    Affected if The installed version is earlier than 9.10.2149, 9.00.2374, or 8.90.2356 (or the version cannot be determined but falls within those release branches)
  2. Verify Alarm Transmitter feature is in use
    Check if the Alarm Transmitter module or feature is configured or enabled within Command Centre. This may be visible in the Command Centre client under System > Features, or via configuration files in the Command Centre data directory
    Affected if The Alarm Transmitter feature is enabled or configured in the environment
  3. Locate Command Centre log files
    Identify the log directory where Command Centre writes its log files. Common paths include the logs folder within the Command Centre installation directory or a dedicated logging directory configured in the system
    Affected if Log files exist and are accessible (this is a prerequisite for the vulnerability to be exploitable)
  4. Inspect log files for sensitive data exposure
    Examine recent log files for security-sensitive information that should be permission-filtered. Look for data that appears to contain credentials, operator actions, or information that should be restricted based on user roles
    Affected if Log files contain sensitive information that may be visible to operators who should not have permission to view that data

You are likely affected if Command Centre is installed with a version prior to the fixed releases AND the Alarm Transmitter feature is enabled, as this creates the condition where unauthorized operators could view restricted data through log files.

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

Apply the vendor-supplied patch (9.10.2149, 9.00.2374, or 8.90.2356 depending on branch) to remediate the improper logging of sensitive information in the Alarm Transmitter feature.

Recommended fix Moderate confidence

Command Centre Server 9.10.2149 (MR4) or later, or 9.00.2374 (MR5), or 8.90.2356 (MR6) depending on current branch

  1. Identify the current Command Centre Server version in use
  2. Determine which version branch is in use (8.80, 8.90, 9.00, or 9.10)
  3. For version 8.80 and prior: Upgrade to Command Centre Server 8.90.2356 (MR6) or later
  4. For version 8.90: Upgrade to Command Centre Server 8.90.2356 (MR6) or later
  5. For version 9.00: Upgrade to Command Centre Server 9.00.2374 (MR5) or later
  6. For version 9.10: Upgrade to Command Centre Server 9.10.2149 (MR4) or later
  7. After upgrade, verify the fix by confirming sensitive information is no longer written to logs in the Alarm Transmitter feature
Caveat Review release notes for the target version to check for any compatibility or configuration changes before upgrading

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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