fix(security): prevent CWE-134 format string injection
All checks were successful
CI Code / Check spelling (pull_request) Successful in 20s
CI Code / Check coding style (pull_request) Successful in 36s
CI Code / Code Coverage (pull_request) Successful in 5m2s
CI Code / Linux (ubuntu) (pull_request) Successful in 6m30s
CI Code / Linux (debian) (pull_request) Successful in 9m5s
CI Code / Linux (arch) (pull_request) Successful in 10m53s
All checks were successful
CI Code / Check spelling (pull_request) Successful in 20s
CI Code / Check coding style (pull_request) Successful in 36s
CI Code / Code Coverage (pull_request) Successful in 5m2s
CI Code / Linux (ubuntu) (pull_request) Successful in 6m30s
CI Code / Linux (debian) (pull_request) Successful in 9m5s
CI Code / Linux (arch) (pull_request) Successful in 10m53s
- add "%s" to unsafe cons_show/log_*/win_println calls - add check-cwe134.sh static analysis script - integrate security check into CI pipeline Closes #85
This commit is contained in:
@@ -168,6 +168,10 @@ num_cores()
|
||||
# Run test failure detection verification first
|
||||
verify_test_failure_detection
|
||||
|
||||
# Run CWE-134 format string vulnerability check
|
||||
echo "=== Running CWE-134 security check ==="
|
||||
./check-cwe134.sh || { echo "CWE-134 check failed!"; exit 1; }
|
||||
|
||||
# Parse arguments
|
||||
COVERAGE_ONLY=no
|
||||
for arg in "$@"; do
|
||||
|
||||
Reference in New Issue
Block a user