Skip to content

Kics

Kics #802

Triggered via schedule February 17, 2025 01:26
Status Failure
Total duration 36s
Artifacts

kics.yaml

on: schedule
Kics Scan
29s
Kics Scan
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 10 warnings
Kics Scan
CodeQL Action major versions v1 and v2 have been deprecated. Please update all occurrences of the CodeQL Action in your workflow files to v3. For more information, see https://github.blog/changelog/2025-01-10-code-scanning-codeql-action-v2-is-now-deprecated/
Kics Scan
KICS scan failed with exit code 50
[HIGH] Passwords And Secrets - Generic Password: .github/workflows/mobile-ios-build.yaml#L279
Query to find passwords and secrets in infrastructure code.
[HIGH] Passwords And Secrets - Generic Token: main.yaml#L276
Query to find passwords and secrets in infrastructure code.
[HIGH] Passwords And Secrets - Generic Token: main.yaml#L547
Query to find passwords and secrets in infrastructure code.
[LOW] Unpinned Actions Full Length Commit SHA: .github/workflows/kics.yaml#L128
Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps mitigate the risk of a bad actor adding a backdoor to the action's repository, as they would need to generate a SHA-1 collision for a valid Git object payload. When selecting a SHA, you should verify it is from the action's repository and not a repository fork.
[LOW] Unpinned Actions Full Length Commit SHA: .github/workflows/docker_build.yaml#L286
Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps mitigate the risk of a bad actor adding a backdoor to the action's repository, as they would need to generate a SHA-1 collision for a valid Git object payload. When selecting a SHA, you should verify it is from the action's repository and not a repository fork.
[LOW] Unpinned Actions Full Length Commit SHA: .github/workflows/pluto.yaml#L56
Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps mitigate the risk of a bad actor adding a backdoor to the action's repository, as they would need to generate a SHA-1 collision for a valid Git object payload. When selecting a SHA, you should verify it is from the action's repository and not a repository fork.
[LOW] Unpinned Actions Full Length Commit SHA: main.yaml#L821
Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps mitigate the risk of a bad actor adding a backdoor to the action's repository, as they would need to generate a SHA-1 collision for a valid Git object payload. When selecting a SHA, you should verify it is from the action's repository and not a repository fork.
[LOW] Unpinned Actions Full Length Commit SHA: main.yaml#L834
Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps mitigate the risk of a bad actor adding a backdoor to the action's repository, as they would need to generate a SHA-1 collision for a valid Git object payload. When selecting a SHA, you should verify it is from the action's repository and not a repository fork.
[LOW] Unpinned Actions Full Length Commit SHA: .github/workflows/dockerhub_build.yaml#L141
Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps mitigate the risk of a bad actor adding a backdoor to the action's repository, as they would need to generate a SHA-1 collision for a valid Git object payload. When selecting a SHA, you should verify it is from the action's repository and not a repository fork.
[LOW] Unpinned Actions Full Length Commit SHA: .github/workflows/tfsec.yaml#L65
Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps mitigate the risk of a bad actor adding a backdoor to the action's repository, as they would need to generate a SHA-1 collision for a valid Git object payload. When selecting a SHA, you should verify it is from the action's repository and not a repository fork.