Compliance-script modification via insecure temporary directory
Published Jan 2, 2025 · Updated Jun 3, 2025
Insecure temporary-directory permissions in Forescout SecureConnector 11.3.07.0109 through 11.3.11 allow local users to alter compliance scripts. Affected builds place compliance scripts beneath the Windows temporary directory without preventing unauthorized modification. The Windows-only path lets local users inject content before the agent runs a script, compromising compliance results and downstream actions.
Summary
What happened
Insecure temporary-directory permissions in Forescout SecureConnector 11.3.07.0109 through 11.3.11 allow local users to alter compliance scripts. Affected builds place compliance scripts beneath the Windows temporary directory without preventing unauthorized modification. The Windows-only path lets local users inject content before the agent runs a script, compromising compliance results and downstream actions.
The record
- CVE
- CVE-2024-9950
- Published
- Jan 2, 2025
- Updated
- Jun 3, 2025
- Vendor
- Forescout
- Product
- Forescout SecureConnector
- Classifications
- CWE-379, CAPEC-23, T1059
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 2, 2025CVE publishedPublication date reported by the CVE source.
- Jun 3, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=v11.3.07.0109 <=v11.3.11
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo