We actively support security updates for the following versions:
| Version | Supported |
|---|---|
| 1.x.x | ✅ |
If you discover a security vulnerability in this project, please follow these steps:
-
Do NOT open a public GitHub issue for security vulnerabilities.
-
Report the vulnerability using one of these methods:
- Preferred: Create a GitHub Security Advisory (requires GitHub account)
- Alternative: Contact the maintainer via GitHub (username:
@ghotso)
-
Include the following information in your report:
- Description of the vulnerability
- Steps to reproduce the issue
- Potential impact and severity
- Suggested fix (if you have one)
-
We will acknowledge receipt of your report within 48 hours.
-
We will provide a detailed response within 7 days indicating the next steps in handling your report.
-
We will keep you informed of the progress towards a fix and full announcement.
-
After the vulnerability has been resolved, we will:
- Credit you in the security advisory (if you wish)
- Update the CHANGELOG.md with the fix
- Release a patched version
This integration follows security best practices:
- Secure Storage: Credentials are stored using Home Assistant's built-in credential store
- Encrypted Communication: All API communication uses HTTPS/TLS
- Authentication: Uses pCloud's digest authentication with SHA1 hashing
- No Plain Text Passwords: Passwords are never sent in plain text
- Token Management: Authentication tokens are securely managed and refreshed
In Scope (vulnerabilities we will investigate):
- Authentication bypass
- Credential exposure or leakage
- API security issues
- Data encryption weaknesses
- Unauthorized access to backups
Out of Scope (issues we typically won't address):
- Denial of service (DoS) attacks
- Social engineering attacks
- Physical security issues
- Issues in Home Assistant core or pCloud's infrastructure
Security updates are released as soon as possible after a vulnerability is confirmed and a fix is available. Critical security fixes will be prioritized and released as patch versions (e.g., 0.0.X).
We appreciate the security research community's efforts to help keep our software secure. Responsible disclosure helps protect users and the project.
Note: For non-security bugs, please use the GitHub Issues page.