A remote code execution vulnerability exists in the Windows agent component of SecureConnector due to improper access controls on a named pipe. The pipe is accessible to the Everyone group and does not restrict remote connections, allowing any network-based attacker to connect wi...
Product
forescout secureconnector vulnerabilities
8 published CVES affecting forescout secureconnector, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).
- Total
- 8
- Critical
- 0
- High
- 6
- Medium
- 2
- Low
- 0
- Unscored
- 0
- CISA KEV
- 0
Latest forescout secureconnector CVEs
Newest publication first
-
HighCVSS 8.7 EPSS 1.2%
-
HighCVSS 8.5 EPSS 0.31%
A vulnerability in Forescout SecureConnector v11.3.07.0109 on Windows allows unauthenticated user to modify compliance scripts due to insecure temporary directory.
-
MediumCVSS 5.8 EPSS 0.14%
Denial of Service in Forescout SecureConnector 11.1.02.1019 on Windows allows Unprivileged user to corrupt the configuration file and cause Denial of Service in the application.
-
HighCVSS 7.0 EPSS 0.31%
Insecure Permissions vulnerability in Forescout SecureConnector v.11.3.06.0063 allows a local attacker to escalate privileges via the Recheck Compliance Status component.
-
HighCVSS 7.8 EPSS 0.20%
ForeScout NAC SecureConnector version 11.2 - CWE-427: Uncontrolled Search Path Element
-
MediumCVSS 5.5 EPSS 0.22%
ForeScout - SecureConnector Local Service DoS - A low privilaged user which doesn't have permissions to shutdown the secure connector service writes a large amount of characters in the installationPath. This will cause the buffer to overflow and override the stack cookie causing...
-
HighCVSS 7.8 EPSS 1.3%
On Windows endpoints, the SecureConnector agent must run under the local SYSTEM account or another administrator account in order to enable full functionality of the agent. The typical configuration is for the agent to run as a Windows service under the local SYSTEM account. The...
-
HighCVSS 7.8 EPSS 1.3%
On Windows endpoints, the SecureConnector agent must run under the local SYSTEM account or another administrator account in order to enable full functionality of the agent. The typical configuration is for the agent to run as a Windows service under the local SYSTEM account. The...
Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.