We release patches for security vulnerabilities for the following versions:
| Version | Supported |
|---|---|
| 2.0.x | ✅ |
| < 2.0 | ❌ |
Please do not report security vulnerabilities through public GitHub issues.
Instead, please report them via email to the maintainers at:
- Create a Security Advisory
- Or email: [maintainer email - update this]
You should receive a response within 48 hours. If for some reason you do not, please follow up to ensure we received your original message.
Please include the following information:
- Type of issue (e.g. buffer overflow, SQL injection, cross-site scripting, etc.)
- Full paths of source file(s) related to the manifestation of the issue
- The location of the affected source code (tag/branch/commit or direct URL)
- Any special configuration required to reproduce the issue
- 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 the issue
When using macOS Fingerprint:
- Encrypt sensitive fingerprints: Use
--encryptflag for sensitive data - Secure storage: Store fingerprints in secure locations with proper permissions
- Regular updates: Keep the tool updated to get latest security patches
- Review changes: Always review fingerprint comparisons for suspicious changes
- Limit access: Restrict who can create/compare fingerprints in your organization
- This tool collects system information including network configurations and installed applications
- By default, sensitive fields (IPs, MACs) are hashed using SHA-3
- Encryption uses AES-256-GCM with password-based key derivation
- All subprocess calls use safe command execution (no shell injection)
- File operations include path sanitization to prevent traversal attacks
- Security issues are triaged within 48 hours
- Patches are developed and tested privately
- Security advisories are published
- Fixes are released as patch versions
- Users are notified through GitHub releases and advisories