docs/EN/SECURITY.md

Security Policy

Supported Versions

We release patches for security vulnerabilities. Which versions are eligible for receiving such patches depends on the CVSS v3.0 Rating:

Version	Supported
1.0.x	:white_check_mark:
< 1.0	:x:

Reporting a Vulnerability

Please do not report security vulnerabilities through public GitHub issues.

Instead, please report them via email to: [INSERT SECURITY EMAIL]

You should receive a response within 48 hours. If for some reason you do not, please follow up via email to ensure we received your original message.

Please include the following information (as much as you can provide) to help us better understand the nature and scope of the possible issue:

• Type of issue (e.g. buffer overflow, SQL injection, cross-site scripting, etc.)
• Full paths of source file(s) related to the manifestation of the issue
• The location of the affected source code (tag/branch/commit or direct URL)
• Any special configuration required to reproduce the issue
• Step-by-step instructions to reproduce the issue
• Proof-of-concept or exploit code (if possible)
• Impact of the issue, including how an attacker might exploit the issue

This information will help us triage your report more quickly.

Preferred Languages

We prefer all communications to be in English or Thai.

Security Update Process

1. Report received - We acknowledge receipt within 48 hours
2. Investigation - We investigate and validate the vulnerability
3. Fix development - We develop and test a fix
4. Security advisory - We publish a security advisory if needed
5. Release - We release a patched version
6. Disclosure - We publicly disclose the vulnerability after the fix is released

Known Security Considerations

File System Access

This application requires file system access to:

• Read Markdown files
• Write exported video files
• Access workspace directory

Mitigations:

• All file operations go through security-core.js with path validation
• Rate limiting prevents abuse
• User consent required for file operations

Electron Security

We follow Electron security best practices:

• Context isolation enabled
• Node integration disabled in renderer
• Preload scripts for IPC communication
• Content Security Policy enforced

Third-Party Dependencies

We regularly:

• Update dependencies to latest secure versions
• Run npm audit to check for vulnerabilities
• Review dependency licenses and security advisories

---