We release patches for security vulnerabilities. The following versions are currently being supported with security updates:
| Version | Supported |
|---|---|
| 1.x.x | ✅ |
| < 1.0 | ❌ |
We take the security of Product-FARM 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 email to:
[email protected] (replace with your security contact email)
Please include the following information in your report:
- Type of vulnerability (e.g., SQL injection, XSS, authentication bypass, etc.)
- Location of the vulnerability (file path, URL, API endpoint, etc.)
- Step-by-step instructions to reproduce the issue
- Proof-of-concept or exploit code (if possible)
- Impact of the vulnerability (what an attacker could achieve)
- Suggested fix (if you have one)
- Acknowledgment: We will acknowledge receipt of your vulnerability report within 48 hours.
- Communication: We will keep you informed of the progress towards a fix.
- Resolution: We aim to resolve critical vulnerabilities within 7-14 days.
- Disclosure: We will coordinate with you on the disclosure timeline.
We consider security research and vulnerability disclosure activities conducted consistent with this policy to be:
- Authorized in accordance with any applicable anti-hacking laws
- Exempt from restrictions in our Terms of Service that would interfere with conducting security research
We will not pursue civil action or initiate a complaint to law enforcement for accidental, good-faith violations of this policy.
When deploying Product-FARM, we recommend the following security measures:
- API Authentication: Implement proper authentication (JWT, OAuth2) for all API endpoints
- Rate Limiting: Enable rate limiting to prevent abuse
- Input Validation: All inputs are validated, but additional validation at the application layer is recommended
- HTTPS: Always use HTTPS in production
- Database Security: Secure your DGraph instance with authentication and network policies
- CORS Configuration: Configure CORS to allow only trusted origins
- Content Security Policy: Implement CSP headers
- XSS Prevention: The React frontend uses proper escaping, but be careful with
dangerouslySetInnerHTML
- Network Isolation: Run services in isolated network segments
- Secrets Management: Use environment variables or secret managers for sensitive configuration
- Logging & Monitoring: Enable audit logging and monitor for suspicious activity
- Regular Updates: Keep all dependencies up to date
JSON Logic expressions are evaluated in a sandboxed environment. However:
- Avoid storing sensitive data in rule expressions
- Review rules before promoting to production
- Consider implementing rule review workflows
- Rule evaluation is CPU-bound; complex rules could be used for DoS attacks
- Implement timeouts for rule evaluation in production
- Consider rate limiting the evaluation API
- DGraph does not encrypt data at rest by default
- Consider enabling encryption for sensitive deployments
- Implement proper backup and recovery procedures
Security updates will be announced through:
- GitHub Security Advisories
- Release notes
- Direct notification to known affected parties
We appreciate the security research community's efforts in helping keep Product-FARM secure. Contributors who report valid security issues will be acknowledged (with their permission) in our release notes.
Thank you for helping keep Product-FARM and its users safe!