# CVE-2024-9950: Abuse of Unauthenticated Compliance Recheck in SecureConnector

> Unauthenticated attackers can modify compliance scripts via insecure temporary directories, potentially leading to code execution or privilege escalation.

- **Severity:** High 8.5 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:L/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Jan 2025
- **Updated:** 3 Jun 2025
- **Also known as:** GHSA-wc69-m7g2-2pcm

## What is CVE-2024-9950?

CVE-2024-9950 is a high-severity path traversal vulnerability in Forescout SecureConnector, published on 2 Jan 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability in Forescout SecureConnector v11.3.07.0109 on Windows allows 

unauthenticated user to modify compliance scripts due to insecure temporary directory.

Weakness: CWE-379 (Creation of Temporary File in Directory with Insecure Permissions)

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

It affects 1 product.


Products: Forescout Secureconnector.

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

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

## Is CVE-2024-9950 being exploited?

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

Public exploit code:

- Forescout SecureConnector <= 11.3.07 (github_poc): https://github.com/0Nightsedge0/CVE-2024-9950-PoC

## Other vulnerabilities in Forescout SecureConnector

- [CVE-2025-4660](https://insights.sbomify.com/CVE-2025-4660/): Remote Code Execution in Windows Secure Connector/ HPS Inspection Engine via Insecure Named Pipe Access (high 8.7)
- [CVE-2023-39374](https://insights.sbomify.com/CVE-2023-39374/): ForeScout NAC SecureConnector – CWE-427: Uncontrolled Search Path Element (high 7.8)
- [CVE-2016-9485](https://insights.sbomify.com/CVE-2016-9485/): Privilege escalation in Windows SecureConnector agent (high 7.8)
- [CVE-2016-9486](https://insights.sbomify.com/CVE-2016-9486/): Privilege escalation in Windows SecureConnector agent (high 7.8)
- [CVE-2024-22795](https://insights.sbomify.com/CVE-2024-22795/): Privilege escalation in n/a (high 7.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-9950 is a high-severity path traversal vulnerability in Forescout SecureConnector, published on 2 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-9950 in the wild and no public exploit code.

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

## Sources

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

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