We actively support the following versions with security updates:
| Version | Supported |
|---|---|
| 5.x | ✅ Fully supported |
| 4.x | Security fixes only |
| < 4.0 | ❌ |
If you discover a security vulnerability in this library, please report it responsibly:
DO NOT open a public issue for security vulnerabilities.
The preferred way to report a vulnerability is GitHub Private vulnerability reporting.
As a backup, email security details to: tomasmajer@gmail.com
Include:
- Description of the vulnerability
- Steps to reproduce
- Potential impact
- Suggested fix (if any)
- Acknowledgment: Within 14 days
- Initial Response: Within 48 hours
- Fix Timeline: Critical issues within 7 days, others within 30 days
- Public Disclosure: After fix is released and users have time to update
We follow coordinated disclosure. When a fix is ready, we publish a GitHub Security Advisory and record the security fix in the CHANGELOG.
When using this library:
- PGP Keys: Store PGP private keys outside web root
- Credentials: Use environment variables for sensitive configuration
- Validation: Always validate extracted amounts before processing payments
- Error Messages: Never expose raw email content in error messages
- Logging: Log parsing failures for security monitoring
- Updates: Keep the library and dependencies up to date
This library parses email content that may contain:
- Financial transaction data
- Account numbers (IBAN)
- Banking symbols (VS, KS, SS)
Always:
- Validate parsed data before use
- Sanitize output when displaying to users
- Store processed data securely
- Comply with GDPR and local data protection regulations
The TatraBankaStatementMailParser decrypts PGP-encrypted emails:
- Ensure private keys are stored securely
- Use strong passphrases
- Rotate keys regularly
- Restrict file system access to key files
- Critical vulnerabilities: Emergency release within 48 hours
- High severity: Release within 7 days
- Medium severity: Included in next regular release
- Low severity: Documented and fixed in future versions
We appreciate security researchers who responsibly disclose vulnerabilities. Contributors will be acknowledged in release notes (unless they prefer to remain anonymous).