-
Notifications
You must be signed in to change notification settings - Fork 1
Security Issues
Paksh Patel edited this page Nov 2, 2025
·
2 revisions
- Data stored includes:
- User credentials
- JWT authentication tokens
- Blender object JSONs and mesh data
- Project history and logs
-
Protection plan:
- Passwords hashed using bcrypt.
- JWT tokens with limited lifespan and refresh system.
- HTTPS for all client-server communication.
- Private, access-restricted MinIO buckets per project.
| Threat | Example | Mitigation |
|---|---|---|
| SQL Injection | Unsanitized database input | Use ORM (SQLAlchemy) and parameterized queries |
| Cross-Site Scripting (XSS) | Malicious script injection | Sanitize all user input and enforce CSP |
| Cross-Site Request Forgery (CSRF) | Forged web requests | Use CSRF tokens on sensitive operations |
| Privilege Escalation | Unauthorized admin actions | Enforce strict role-based access control |
| Path Traversal | Malicious file access | Validate file paths and sanitize uploads |
- Backend and database run in isolated Docker containers.
- Regular dependency updates and security patches.
- API rate limiting and logging to detect suspicious activity.
- Enforced access control for all cloud and database resources.
In the event of a security breach:
- Log and investigate all events.
- Notify affected users promptly.
- Patch vulnerabilities and review system access.