Forescout

Secureconnector

8 Schwachstellen gefunden.

Hinweis: Diese Liste kann unvollständig sein. Daten werden ohne Gewähr im Ursprungsformat bereitgestellt.
  • EPSS 0.68%
  • Veröffentlicht 13.05.2025 17:34:53
  • Zuletzt bearbeitet 15.05.2025 18:38:32

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 networ...

  • EPSS 1.77%
  • Veröffentlicht 02.01.2025 16:15:08
  • Zuletzt bearbeitet 17.10.2025 18:13:19

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

  • EPSS 0.15%
  • Veröffentlicht 23.10.2024 18:15:13
  • Zuletzt bearbeitet 09.10.2025 15:35:02

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.

Exploit
  • EPSS 0.13%
  • Veröffentlicht 08.02.2024 19:15:08
  • Zuletzt bearbeitet 05.06.2025 16:15:26

Insecure Permissions vulnerability in Forescout SecureConnector v.11.3.06.0063 allows a local attacker to escalate privileges via the Recheck Compliance Status component.

  • EPSS 0.05%
  • Veröffentlicht 03.09.2023 15:15:14
  • Zuletzt bearbeitet 21.11.2024 08:15:16

ForeScout NAC SecureConnector version 11.2 - CWE-427: Uncontrolled Search Path Element

  • EPSS 0.04%
  • Veröffentlicht 29.12.2021 18:15:07
  • Zuletzt bearbeitet 21.11.2024 06:13:59

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 over...

  • EPSS 0.22%
  • Veröffentlicht 13.07.2018 20:29:01
  • Zuletzt bearbeitet 21.11.2024 03:01:18

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 ...

  • EPSS 0.39%
  • Veröffentlicht 13.07.2018 20:29:01
  • Zuletzt bearbeitet 21.11.2024 03:01:18

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 ...