| Version | Supported |
|---|---|
| 1.0.x | ✅ |
We take the security of DeviceMocker 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:
-
GitHub Security Advisories (preferred)
- Go to https://github.com/x1n-Q/DeviceMocker/security/advisories
- Click "Report a vulnerability"
- Fill out the form with details
-
Email (alternative)
- Send an email to the project maintainer
- Use subject line:
[SECURITY] DeviceMocker - <brief description>
Please include the following information in your report:
- Type of vulnerability (e.g., buffer overflow, SQL injection, XSS)
- Affected component (e.g., SerialOutputService, KeyboardOutputService)
- Steps to reproduce with detailed instructions
- Proof of concept or exploit code (if available)
- Potential impact - what could an attacker achieve?
- Suggested fix (if you have one)
- Acknowledgment: Within 48 hours of receipt
- Initial assessment: Within 7 days
- Resolution timeline: Varies based on severity
- Critical: 7 days
- High: 14 days
- Medium: 30 days
- Low: 90 days
- We will acknowledge receipt of your report
- We will investigate and validate the vulnerability
- We will work on a fix and coordinate release
- We will credit you (unless you prefer to remain anonymous)
- We will publish a security advisory
DeviceMocker uses several Windows APIs that require careful handling:
- Windows SendInput API - Used for keyboard simulation
- Serial Port Communication - Direct hardware access
- Network Sockets - TCP/UDP communication
- HTTP Requests - Webhook functionality
Please consider these when testing and reporting vulnerabilities.
We ask that you:
- Give us reasonable time to fix the issue before public disclosure
- Avoid exploiting the vulnerability beyond what's necessary to demonstrate it
- Not use the vulnerability to access, modify, or delete data
- Make a good faith effort to avoid privacy violations and service disruption
Thank you for helping keep DeviceMocker and its users safe!