Skip to content

Bump step-security/harden-runner from 2.7.1 to 2.8.0 #91

Bump step-security/harden-runner from 2.7.1 to 2.8.0

Bump step-security/harden-runner from 2.7.1 to 2.8.0 #91

Triggered via pull request June 1, 2024 19:45
Status Success
Total duration 2m 29s
Artifacts

linter.yml

on: pull_request
cpp-linter
39s
cpp-linter
Fit to window
Zoom out
Zoom in

Annotations

10 errors and 10 warnings
tee/tee/tee_obj.c:29:10 [clang-diagnostic-error]: tee/tee/tee_obj.c#L29
'tee/tee_obj.h' file not found
tools/mkconfig.c:58:3 [clang-analyzer-security.insecureAPI.DeprecatedOrUnsafeBufferHandling]: tools/mkconfig.c#L58
Call to function 'snprintf' is insecure as it does not provide security checks introduced in the C11 standard. Replace with analogous functions that support length arguments or provides boundary checks such as 'snprintf_s' in case of C11
tools/mkconfig.c:75:9 [cppcoreguidelines-init-variables]: tools/mkconfig.c#L75
variable 'filepath' is not initialized
tools/mkconfig.c:76:9 [cppcoreguidelines-init-variables]: tools/mkconfig.c#L76
variable 'stream' is not initialized
tools/ecdsa_keygen.c:62:16 [bugprone-reserved-identifier]: tools/ecdsa_keygen.c#L62
declaration uses identifier '_AES_DATA', which is a reserved identifier
tools/ecdsa_keygen.c:120:3 [clang-analyzer-security.insecureAPI.DeprecatedOrUnsafeBufferHandling]: tools/ecdsa_keygen.c#L120
Call to function 'memcpy' is insecure as it does not provide security checks introduced in the C11 standard. Replace with analogous functions that support length arguments or provides boundary checks such as 'memcpy_s' in case of C11
tools/ecdsa_keygen.c:121:3 [clang-analyzer-security.insecureAPI.DeprecatedOrUnsafeBufferHandling]: tools/ecdsa_keygen.c#L121
Call to function 'memcpy' is insecure as it does not provide security checks introduced in the C11 standard. Replace with analogous functions that support length arguments or provides boundary checks such as 'memcpy_s' in case of C11
tools/ecdsa_keygen.c:136:5 [clang-analyzer-unix.Malloc]: tools/ecdsa_keygen.c#L136
Potential leak of memory pointed to by 'encrypted_message'