Sourced from github.com/agilira/flash-flags's releases.

v1.1.5: Security Hardening and Performance Optimization

CHANGELOG v1.1.5

Release Date: 2025-10-08

SECURITY ENHANCEMENTS

• Added comprehensive input validation system with validateSecurityConstraints function
• Implemented protection against command injection attacks
• Added path traversal prevention mechanisms
• Implemented buffer overflow safeguards with 10KB input limits
• Added format string attack detection and blocking
• Implemented null byte injection prevention
• Added control character validation and filtering
• Added Windows device name protection (CON, PRN, AUX, etc.)

PERFORMANCE OPTIMIZATIONS

• Optimized security validation with fast-path for simple alphanumeric inputs
• Implemented isSimpleAlphanumeric function for performance-critical paths
• Reduced security overhead from 3407ns to 924ns per operation
• Achieved 85% of stdlib performance while maintaining full security
• Optimized memory allocation patterns

TESTING INFRASTRUCTURE

• Added comprehensive fuzz testing suite with 5 fuzz functions
• Implemented FuzzParse for core parsing security validation
• Added FuzzParseStringSlice for slice parsing security
• Implemented FuzzLoadConfig for configuration loading security
• Added FuzzEnvironmentVariables for environment variable security
• Implemented FuzzFlagValidation for validation system security
• Added security benchmark testing suite
• Implemented BenchmarkParse_Typical and BenchmarkSecurityOverhead_Minimal

DEVELOPMENT WORKFLOW IMPROVEMENTS

• Added CodeQL security analysis workflow with custom queries
• Implemented automated security scanning on push and pull requests
• Added scheduled security scans (daily at 02:00 UTC)
• Created custom CodeQL queries for command-line parsing vulnerabilities
• Implemented CommandInjection.ql, PathTraversal.ql, and BufferOverflow.ql
• Added comprehensive CodeQL configuration with flash-flags specific rules
• Updated Makefile and Makefile.ps1 with correct fuzz test references
• Added security policy enforcement configuration

... (truncated)

• 5e5183b v1.1.5: Security hardening with comprehensive fuzz testing and CodeQL integra...
• See full diff in compare view

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions