# CVE-2024-42407: Information disclosure in Command Centre Server

> An authenticated operator can view sensitive security information via log files in Gallagher Command Centre, requiring an upgrade to fix.

- **Severity:** High 8.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Dec 2024
- **Updated:** 12 Dec 2024
- **Also known as:** GHSA-8fqw-xqvx-7f2j

## What is CVE-2024-42407?

CVE-2024-42407 is a high-severity vulnerability in Gallagher Command Centre Server, published on 12 Dec 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File)

## Which versions are affected by CVE-2024-42407?


## How do I fix CVE-2024-42407?

No fix has been published for CVE-2024-42407 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-42407 being exploited?

There is no known exploitation of CVE-2024-42407 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-42407 and fix it if it is affected.

What it is: CVE-2024-42407 is a high-severity vulnerability in Gallagher Command Centre Server, published on 12 Dec 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-42407 in the wild and no public exploit code.

Affected product: Gallagher Command Centre Server. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-42407/ (Markdown: https://insights.sbomify.com/CVE-2024-42407/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-42407
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-42407
- OSV: https://osv.dev/vulnerability/CVE-2024-42407

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-42407/
Summaries are generated and may contain mistakes; the official description above is the record.