Security fixes go into the latest release on the PowerShell Gallery:
| Version | Supported |
|---|---|
| Latest release (0.5.x) | ✅ |
| Older releases | ❌ |
We take the security of ConnectWiseControlAPI seriously. If you believe you have found a security vulnerability, please report it to us as described below.
Please do NOT report security vulnerabilities through public GitHub issues.
Instead, please report them via one of the following methods:
-
Direct Email (Preferred)
- Send an email to: security@christaylor.codes
- Use the subject line:
[SECURITY] ConnectWiseControlAPI - Brief Description
-
Private Message on Slack
- Contact @CTaylor on MSPGeek Slack
- Clearly mark the message as security-related
Please include the following information in your report to help us better understand and resolve the issue:
- Type of issue (e.g., credential exposure, injection, privilege escalation)
- Full paths of source file(s) related to the manifestation of the issue
- Location of the affected source code (tag/branch/commit or direct URL)
- Step-by-step instructions to reproduce the issue
- Proof-of-concept or exploit code (if possible)
- Impact of the issue, including how an attacker might exploit it
- Your assessment of severity (Critical, High, Medium, Low)
After you submit a vulnerability report:
- Acknowledgment - We will acknowledge receipt of your vulnerability report within 48 hours
- Initial Assessment - We will provide an initial assessment of the vulnerability within 5 business days
- Updates - We will keep you informed of the progress toward a fix and full announcement
- Verification - We may ask you to verify that our fix resolves the vulnerability
- Public Disclosure - We will coordinate with you on the timing of public disclosure
- Credit - We will credit you in the security advisory (unless you prefer to remain anonymous)
We use the CVSS v3.1 scoring system to assess vulnerability severity:
- Critical (9.0-10.0) - Fix within 24-48 hours
- High (7.0-8.9) - Fix within 1 week
- Medium (4.0-6.9) - Fix within 2-4 weeks
- Low (0.1-3.9) - Fix in next regular release
When using this module, please:
-
Secure Your Credentials
- Never commit API credentials or passwords to source control
- Use PowerShell
[PSCredential]objects, not plaintext passwords - Use a complex username and password; accounts that require MFA sign in with
-Mfa,-OneTimeCodeor-TotpSecret - A TOTP secret for unattended logins (
-TotpSecret) is a second password: keep it in a secret store, apart from the account password where you can, and replace it if the computer is compromised
-
Use HTTPS
- The module requires your ScreenConnect server to use HTTPS
- The module turns TLS 1.2 on for the PowerShell session; it does not turn older versions off
-
Keep Updated
- Regularly update the module from the PowerShell Gallery
- Review the CHANGELOG for security-related fixes
-
PowerShell Execution Policy
- Be cautious when using
-ExecutionPolicy Bypass - Prefer signed scripts in production environments
- Be cautious when using
We appreciate security researchers who responsibly disclose vulnerabilities. Contributors will be listed here (with permission):
No vulnerabilities reported yet.