We actively support the following versions with security updates:
| Version | Supported |
|---|---|
| 1.x.x | β |
| < 1.0 | β |
Please do NOT report security vulnerabilities through public GitHub issues.
- Go to the Security Advisories page
- Click "Report a vulnerability"
- Fill in the details using the template below
Send an email to: security@karting.example.com
Please include the following information in your report:
- Type of vulnerability (e.g., SQL injection, XSS, CSRF, authentication bypass)
- Affected component (e.g., API endpoint, frontend route, specific file)
- Steps to reproduce (detailed, numbered steps)
- Proof of concept (code, screenshots, or demo)
- Impact assessment (what an attacker could do)
- Suggested fix (if you have one)
- Your name/handle (for credit, if desired)
## Vulnerability Type
SQL Injection
## Affected Component
POST /api/sessions/upload-eml
## Impact
An attacker could execute arbitrary SQL queries.
## Steps to Reproduce
1. Send POST request to /api/sessions/upload-eml
2. Include malicious payload in filename parameter
3. Database query executes with unsanitized input
## Proof of Concept
[Include code, curl command, or screenshot]
## Suggested Fix
Use prepared statements with parameter binding.We aim to respond to security reports according to the following timeline:
| Action | Timeline |
|---|---|
| Initial Response | Within 24 hours |
| Severity Assessment | Within 48 hours |
| Fix Development | 7-14 days (depending on severity) |
| Fix Release | As soon as possible after fix |
| Public Disclosure | After fix is released and deployed |
We classify vulnerabilities using the following severity levels:
- Remote code execution
- Authentication bypass
- SQL injection leading to full database access
- Fix Timeline: 24-48 hours
- XSS allowing account takeover
- CSRF with significant impact
- Privilege escalation
- Fix Timeline: 3-7 days
- Information disclosure
- XSS (non-persistent)
- Weak cryptography
- Fix Timeline: 7-14 days
- Minor information leaks
- Security misconfigurations
- Fix Timeline: 14-30 days
When using this application, follow these security best practices:
- Use HTTPS/TLS in production
- Enable all security headers (CSP, X-Frame-Options, etc.)
- Configure CORS whitelist for production domains only
- Use strong, unique database passwords
- Enable database encryption at rest
- Use httpOnly cookies for authentication
- Set appropriate session timeouts
- Enable rate limiting on all API endpoints
- Never commit
.envfiles to version control - Rotate API keys and secrets regularly
- Use environment variables for sensitive data
- Disable debug mode in production (
APP_DEBUG=false) - Set
APP_ENV=productionin production - Configure Sentry for error tracking
- Enable audit logging for sensitive operations
- Keep dependencies up-to-date (run
composer update,npm update) - Monitor security advisories (GitHub Dependabot)
- Apply security patches promptly
- Subscribe to Laravel security notifications
- Review and update security policies quarterly
This application includes the following built-in security features:
- β Authentication: Laravel Sanctum with session-based auth (httpOnly cookies)
- β Authorization: Role-based access control (admin/driver)
- β CSRF Protection: Enabled for all state-changing operations
- β XSS Protection: Input sanitization via InputSanitizer service
- β SQL Injection Protection: Eloquent ORM with prepared statements
- β Rate Limiting: IP-based (60/min) + per-user (120/min)
- β Password Security: bcrypt hashing with enforced policy
- β Security Headers: CSP, X-Frame-Options, X-Content-Type-Options, HSTS
- β Audit Logging: All CRUD operations logged with user context
- β File Validation: MIME type, size, content pattern checks
- β Error Tracking: Sentry integration for production monitoring
- OWASP Top 10
- Laravel Security Documentation
- Vue.js Security Best Practices
- NIST Cybersecurity Framework
We thank the following security researchers for responsibly disclosing vulnerabilities:
- No vulnerabilities reported yet
For non-security issues, please use:
- GitHub Issues: https://github.com/TheMaksoo/karting/issues
- Discussions: https://github.com/TheMaksoo/karting/discussions
For security concerns only:
- Email: security@karting.example.com
- GitHub Security Advisories: https://github.com/TheMaksoo/karting/security/advisories
Thank you for helping keep Karting Dashboard secure! π