dbcve.org
SecureconnectorApplication · Forescout

CVE-2024-9950

HIGH · 7.8 CVSS v3.1 Published 2025-01-02
Fix available
A fix is available. Upgrade to 11.3.12 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

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

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Forescout SecureConnector v11.3.07.0109 on Windows uses an insecure temporary directory for handling compliance scripts, allowing unauthenticated local users to modify these scripts. This likely stems from the application using a world-writable temp location (e.g., %TEMP% with improper ACLs or a predictable temp path), enabling a race condition or direct tampering that can lead to arbitrary code execution with elevated privileges when compliance scripts are executed.

MitigationRestrict permissions on the temporary directory used by SecureConnector, or upgrade to a version that uses secure temporary file handling (e.g., using Windows API GetTempPath with proper ACLs). Verify compliance scripts cannot be modified by non-admin users.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
SecureconnectorApplication
Affected:>= 11.3.07.0109, < 11.3.12

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Forescout SecureConnector is installed
    Check for SecureConnector installation on the Windows system - look in Program Files or Program Files (x86) for a Forescout folder, or check Windows Services for a SecureConnector service
    Affected if SecureConnector is present on the system
  2. Determine installed SecureConnector version
    Use Windows Registry or program information to find the exact version number - check HKLM\SOFTWARE\Forescout\SecureConnector or the program's version info in the installation directory
    Affected if Version is >= 11.3.07.0109 and < 11.3.12
  3. Locate the temporary directory used by SecureConnector
    Examine process behavior or configuration to find where SecureConnector stores temporary files during compliance script handling - this may be the system TEMP folder (%TEMP% or %TMP%) or a subfolder within the SecureConnector installation
    Affected if Temporary files are stored in a world-writable location accessible to non-admin users
  4. Check permissions on the temporary directory
    Review ACLs on the temp directory used by SecureConnector to determine if non-privileged users have write access - verify if Authenticated Users or Users group have Modify or Write permissions
    Affected if Non-admin users have write/modify permissions to the temp directory
  5. Inspect compliance scripts and their storage location
    Locate compliance scripts handled by SecureConnector and verify their storage location and file permissions - check if scripts are temporarily stored in an unprotected location before execution
    Affected if Compliance scripts are written to or stored in a location writable by non-admin users

A system is affected if Forescout SecureConnector version is between 11.3.07.0109 and 11.3.12 (inclusive) AND the temporary directory used for compliance scripts has weak permissions allowing non-admin users to modify script files before execution.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 11.3.12 or later
Fixed in 11.3.12
Interim mitigation

Restrict permissions on the temporary directory used by SecureConnector, or upgrade to a version that uses secure temporary file handling (e.g., using Windows API GetTempPath with proper ACLs). Verify compliance scripts cannot be modified by non-admin users.

Recommended fix High confidence

SecureConnector 11.3.12 or later

  1. Identify all Windows systems running Forescout SecureConnector with versions 11.3.07.0109 through 11.3.11 using your asset inventory or by checking the SecureConnector version on each endpoint
  2. Obtain SecureConnector version 11.3.12 or later from the Forescout support portal (support.forescout.com) or your designated vendor distribution channel
  3. Test the upgrade in a non-production environment to ensure compatibility with your existing Forescout platform and managed systems
  4. Apply the upgrade to production systems following your organization's change management procedures
  5. Verify successful installation by confirming the SecureConnector version displays as 11.3.12 or later on managed endpoints

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Secureconnector Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-9950 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-9950 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data