KICS #11
nitin-vavdiyaAnnotations
10 warnings
|
[MEDIUM] Container Running With Low UID:
charts/ssi-credential-issuer/templates/cronjob-issuer-processes.yaml#L37
Check if containers are running with low UID, which might cause conflicts with the host's user table.
|
|
[MEDIUM] Container Running With Low UID:
charts/ssi-credential-issuer/templates/deployment-issuer-service.yaml#L39
Check if containers are running with low UID, which might cause conflicts with the host's user table.
|
|
[MEDIUM] Container Running With Low UID:
charts/ssi-credential-issuer/templates/cronjob-expiry-app.yaml#L37
Check if containers are running with low UID, which might cause conflicts with the host's user table.
|
|
[MEDIUM] Seccomp Profile Is Not Configured:
charts/ssi-credential-issuer/templates/cronjob-issuer-processes.yaml#L37
Containers should be configured with a secure Seccomp profile to restrict potentially dangerous syscalls
|
|
[MEDIUM] Seccomp Profile Is Not Configured:
charts/ssi-credential-issuer/templates/deployment-issuer-service.yaml#L39
Containers should be configured with a secure Seccomp profile to restrict potentially dangerous syscalls
|
|
[MEDIUM] Seccomp Profile Is Not Configured:
charts/ssi-credential-issuer/templates/cronjob-expiry-app.yaml#L37
Containers should be configured with a secure Seccomp profile to restrict potentially dangerous syscalls
|
|
[MEDIUM] Service Account Token Automount Not Disabled:
charts/ssi-credential-issuer/templates/cronjob-issuer-processes.yaml#L35
Service Account Tokens are automatically mounted even if not necessary
|
|
[MEDIUM] Service Account Token Automount Not Disabled:
charts/ssi-credential-issuer/templates/cronjob-expiry-app.yaml#L35
Service Account Tokens are automatically mounted even if not necessary
|
|
[MEDIUM] Service Account Token Automount Not Disabled:
charts/ssi-credential-issuer/templates/deployment-issuer-service.yaml#L38
Service Account Tokens are automatically mounted even if not necessary
|
|
[MEDIUM] Unpinned Actions Full Length Commit SHA:
.github/workflows/chart-test.yml#L92
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.
|