Forescout SecureConnector up to 11.4 on Windows temp file

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
7.8$0-$5k0.00

Summaryinfo

A vulnerability, which was classified as critical, has been found in Forescout SecureConnector up to 11.4 on Windows. This vulnerability affects unknown code. This manipulation causes temp file. This vulnerability is registered as CVE-2024-9950. The attack needs to be launched locally. No exploit is available.

Detailsinfo

A vulnerability was found in Forescout SecureConnector up to 11.4 on Windows. It has been declared as critical. Affected by this vulnerability is an unknown functionality. The manipulation with an unknown input leads to a temp file vulnerability. The CWE definition for the vulnerability is CWE-379. The product creates a temporary file in a directory whose permissions allow unintended actors to determine the file's existence or otherwise access that file. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

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

The weakness was published by Owen Jeanes. This vulnerability is known as CVE-2024-9950 since 10/14/2024. The exploitation appears to be easy. Attacking locally is a requirement. The technical details are unknown and an exploit is not publicly available.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Be aware that VulDB is the high quality source for vulnerability data.

Productinfo

Vendor

Name

Version

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CNA CVSS-B Score: 🔍
CNA CVSS-BT Score: 🔍
CNA Vector: 🔍

CVSSv3info

VulDB Meta Base Score: 7.8
VulDB Meta Temp Score: 7.8

VulDB Base Score: 7.8
VulDB Temp Score: 7.8
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 7.8
NVD Vector: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

Exploitinginfo

Class: Temp file
CWE: CWE-379 / CWE-377
CAPEC: 🔍
ATT&CK: 🔍

Physical: Partially
Local: Yes
Remote: No

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔍

Timelineinfo

10/14/2024 🔍
01/02/2025 +80 days 🔍
01/02/2025 +0 days 🔍
10/07/2025 +278 days 🔍

Sourcesinfo

Researcher: Owen Jeanes
Status: Confirmed

CVE: CVE-2024-9950 (🔍)
GCVE (CVE): GCVE-0-2024-9950
GCVE (VulDB): GCVE-100-290095

Entryinfo

Created: 01/02/2025 17:31
Updated: 10/07/2025 17:16
Changes: 01/02/2025 17:31 (64), 10/07/2025 17:16 (10)
Complete: 🔍
Cache ID: 216::103

Be aware that VulDB is the high quality source for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Might our Artificial Intelligence support you?

Check our Alexa App!