# CVE-2024-52975: Fleet Server sensitive information exposure via logs

> Attackers with log access can read sensitive information from Fleet policies logged at INFO and ERROR levels in Elastic Fleet Server.

- **Severity:** Critical 9.0 (`CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Jan 2025
- **Updated:** 23 Jan 2025
- **Also known as:** GHSA-5v56-f8rx-2m6r

## What is CVE-2024-52975?

CVE-2024-52975 is a critical vulnerability in Elastic Fleet Server, published on 23 Jan 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An issue was identified in Fleet Server where Fleet policies that could contain sensitive information were logged on INFO and ERROR log levels. The nature of the sensitive information largely depends on the integrations enabled.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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


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

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

## Is CVE-2024-52975 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-52975 is a critical vulnerability in Elastic Fleet Server, published on 23 Jan 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-52975 in the wild and no public exploit code.

Affected product: Elastic Fleet 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-52975/ (Markdown: https://insights.sbomify.com/CVE-2024-52975/index.md)
```

## Sources

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

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