# CVE-2024-11035: Carbon Black Cloud Windows Sensor Information Leak

> An attacker can expose sensitive information from the Carbon Black Cloud Windows Sensor, requiring an upgrade to mitigate the leak.

- **Severity:** Low 2.5 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **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:** 5 Mar 2025
- **Updated:** 5 Mar 2025
- **Also known as:** GHSA-9559-r2q8-77q4

## What is CVE-2024-11035?

CVE-2024-11035 is a low-severity vulnerability in Symantec Carbon Black Cloud Windows Sensor, published on 5 Mar 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Carbon Black Cloud Windows Sensor, prior to 4.0.3, may be susceptible to an Information Leak vulnerability, which s a type of issue whereby sensitive information may b exposed due to a vulnerability in software.

Weakness: CWE-497 (Exposure of Sensitive System Information to an Unauthorized Control Sphere)

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


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

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

## Is CVE-2024-11035 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-11035 is a low-severity vulnerability in Symantec Carbon Black Cloud Windows Sensor, published on 5 Mar 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-11035 in the wild and no public exploit code.

Affected product: Symantec Carbon Black Cloud Windows Sensor. 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-11035/ (Markdown: https://insights.sbomify.com/CVE-2024-11035/index.md)
```

## Sources

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

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