| Version | Supported |
|---|---|
| 0.1.x | ✅ |
If you discover a security vulnerability in asmqdm, please report it responsibly.
- Do not open a public GitHub issue for security vulnerabilities
- Email the maintainer directly or use GitHub's private vulnerability reporting feature
- Include as much detail as possible:
- Description of the vulnerability
- Steps to reproduce
- Potential impact
- Suggested fix (if any)
- Acknowledgment of your report within 48 hours
- Regular updates on the status of the fix
- Credit in the release notes (unless you prefer to remain anonymous)
Security issues of particular concern for this project include:
- Memory safety issues in the Assembly code (buffer overflows, use-after-free)
- Syscall vulnerabilities that could lead to privilege escalation
- Thread safety issues in async mode that could cause data corruption
- Path traversal or arbitrary file access through the shared library loading
The following are generally not considered security vulnerabilities:
- Denial of service through resource exhaustion (e.g., very large iteration counts)
- Issues that require local access with the same privileges as the running process
- Issues in development dependencies not shipped with the package
asmqdm uses direct Linux syscalls and is designed to run only on Linux x86_64 systems. Running on other platforms is unsupported and may have undefined behavior.
The Python wrapper loads libasmqdm.so using ctypes. The library is loaded from:
- The package installation directory
- System library paths
Ensure the shared library comes from a trusted source.
The Assembly code allocates memory via mmap and manages it directly. The Python wrapper ensures proper cleanup through:
- Context manager (
__exit__) - Explicit
close()calls - Reference counting in normal usage
- Install asmqdm from trusted sources (official PyPI package or verified repository)
- Keep the package updated to receive security fixes
- Report any suspicious behavior