Snyk - Open Source Security

Snyk test report

September 17th 2023, 12:18:15 am (UTC+00:00)

Scanned the following path:
  • /argo-cd/manifests/install.yaml (Kubernetes)
40 total issues
Project manifests/install.yaml
Path /argo-cd/manifests/install.yaml
Project Type Kubernetes

Role with dangerous permissions

medium severity

  • Public ID: SNYK-CC-K8S-47
  • Introduced through: [DocId: 10] rules[0] resources
  • Line number: 18488

Impact

Using this role grants dangerous permissions

Remediation

Consider removing this permissions


Role with dangerous permissions

medium severity

  • Public ID: SNYK-CC-K8S-47
  • Introduced through: [DocId: 11] rules[4] resources
  • Line number: 18565

Impact

Using this role grants dangerous permissions

Remediation

Consider removing this permissions


Role with dangerous permissions

medium severity

  • Public ID: SNYK-CC-K8S-47
  • Introduced through: [DocId: 12] rules[0] resources
  • Line number: 18593

Impact

Using this role grants dangerous permissions

Remediation

Consider removing this permissions


Role with dangerous permissions

medium severity

  • Public ID: SNYK-CC-K8S-47
  • Introduced through: [DocId: 13] rules[3] resources
  • Line number: 18641

Impact

Using this role grants dangerous permissions

Remediation

Consider removing this permissions


Role with dangerous permissions

medium severity

  • Public ID: SNYK-CC-K8S-47
  • Introduced through: [DocId: 13] rules[1] resources
  • Line number: 18623

Impact

Using this role grants dangerous permissions

Remediation

Consider removing this permissions


Role with dangerous permissions

medium severity

  • Public ID: SNYK-CC-K8S-47
  • Introduced through: [DocId: 14] rules[0] resources
  • Line number: 18657

Impact

Using this role grants dangerous permissions

Remediation

Consider removing this permissions


Container could be running with outdated image

low severity

  • Public ID: SNYK-CC-K8S-42
  • Introduced through: [DocId: 45] spec template spec initContainers[copyutil] imagePullPolicy
  • Line number: 19790

Impact

The container may run with outdated or unauthorized image

Remediation

Set `imagePullPolicy` attribute to `Always`


Container has no CPU limit

low severity

  • Public ID: SNYK-CC-K8S-5
  • Introduced through: [DocId: 41] input spec template spec containers[argocd-applicationset-controller] resources limits cpu
  • Line number: 19141

Impact

CPU limits can prevent containers from consuming valuable compute time for no benefit (e.g. inefficient code) that might lead to unnecessary costs. It is advisable to also configure CPU requests to ensure application stability.

Remediation

Add `resources.limits.cpu` field with required CPU limit value


Container has no CPU limit

low severity

  • Public ID: SNYK-CC-K8S-5
  • Introduced through: [DocId: 42] input spec template spec initContainers[copyutil] resources limits cpu
  • Line number: 19386

Impact

CPU limits can prevent containers from consuming valuable compute time for no benefit (e.g. inefficient code) that might lead to unnecessary costs. It is advisable to also configure CPU requests to ensure application stability.

Remediation

Add `resources.limits.cpu` field with required CPU limit value


Container has no CPU limit

low severity

  • Public ID: SNYK-CC-K8S-5
  • Introduced through: [DocId: 42] input spec template spec containers[dex] resources limits cpu
  • Line number: 19352

Impact

CPU limits can prevent containers from consuming valuable compute time for no benefit (e.g. inefficient code) that might lead to unnecessary costs. It is advisable to also configure CPU requests to ensure application stability.

Remediation

Add `resources.limits.cpu` field with required CPU limit value


Container has no CPU limit

low severity

  • Public ID: SNYK-CC-K8S-5
  • Introduced through: [DocId: 43] input spec template spec containers[argocd-notifications-controller] resources limits cpu
  • Line number: 19446

Impact

CPU limits can prevent containers from consuming valuable compute time for no benefit (e.g. inefficient code) that might lead to unnecessary costs. It is advisable to also configure CPU requests to ensure application stability.

Remediation

Add `resources.limits.cpu` field with required CPU limit value


Container has no CPU limit

low severity

  • Public ID: SNYK-CC-K8S-5
  • Introduced through: [DocId: 44] input spec template spec containers[redis] resources limits cpu
  • Line number: 19533

Impact

CPU limits can prevent containers from consuming valuable compute time for no benefit (e.g. inefficient code) that might lead to unnecessary costs. It is advisable to also configure CPU requests to ensure application stability.

Remediation

Add `resources.limits.cpu` field with required CPU limit value


Container has no CPU limit

low severity

  • Public ID: SNYK-CC-K8S-5
  • Introduced through: [DocId: 45] input spec template spec initContainers[copyutil] resources limits cpu
  • Line number: 19790

Impact

CPU limits can prevent containers from consuming valuable compute time for no benefit (e.g. inefficient code) that might lead to unnecessary costs. It is advisable to also configure CPU requests to ensure application stability.

Remediation

Add `resources.limits.cpu` field with required CPU limit value


Container has no CPU limit

low severity

  • Public ID: SNYK-CC-K8S-5
  • Introduced through: [DocId: 45] input spec template spec containers[argocd-repo-server] resources limits cpu
  • Line number: 19590

Impact

CPU limits can prevent containers from consuming valuable compute time for no benefit (e.g. inefficient code) that might lead to unnecessary costs. It is advisable to also configure CPU requests to ensure application stability.

Remediation

Add `resources.limits.cpu` field with required CPU limit value


Container has no CPU limit

low severity

  • Public ID: SNYK-CC-K8S-5
  • Introduced through: [DocId: 46] input spec template spec containers[argocd-server] resources limits cpu
  • Line number: 19875

Impact

CPU limits can prevent containers from consuming valuable compute time for no benefit (e.g. inefficient code) that might lead to unnecessary costs. It is advisable to also configure CPU requests to ensure application stability.

Remediation

Add `resources.limits.cpu` field with required CPU limit value


Container has no CPU limit

low severity

  • Public ID: SNYK-CC-K8S-5
  • Introduced through: [DocId: 47] input spec template spec containers[argocd-application-controller] resources limits cpu
  • Line number: 20191

Impact

CPU limits can prevent containers from consuming valuable compute time for no benefit (e.g. inefficient code) that might lead to unnecessary costs. It is advisable to also configure CPU requests to ensure application stability.

Remediation

Add `resources.limits.cpu` field with required CPU limit value


Container is running with multiple open ports

low severity

  • Public ID: SNYK-CC-K8S-36
  • Introduced through: [DocId: 42] spec template spec containers[dex] ports
  • Line number: 19366

Impact

Increases the attack surface of the application and the container.

Remediation

Reduce `ports` count to 2


Container is running without liveness probe

low severity

  • Public ID: SNYK-CC-K8S-41
  • Introduced through: [DocId: 41] spec template spec containers[argocd-applicationset-controller] livenessProbe
  • Line number: 19141

Impact

Kubernetes will not be able to detect if application is able to service requests, and will not restart unhealthy pods

Remediation

Add `livenessProbe` attribute


Container is running without liveness probe

low severity

  • Public ID: SNYK-CC-K8S-41
  • Introduced through: [DocId: 42] spec template spec containers[dex] livenessProbe
  • Line number: 19352

Impact

Kubernetes will not be able to detect if application is able to service requests, and will not restart unhealthy pods

Remediation

Add `livenessProbe` attribute


Container is running without liveness probe

low severity

  • Public ID: SNYK-CC-K8S-41
  • Introduced through: [DocId: 42] spec template spec initContainers[copyutil] livenessProbe
  • Line number: 19386

Impact

Kubernetes will not be able to detect if application is able to service requests, and will not restart unhealthy pods

Remediation

Add `livenessProbe` attribute


Container is running without liveness probe

low severity

  • Public ID: SNYK-CC-K8S-41
  • Introduced through: [DocId: 44] spec template spec containers[redis] livenessProbe
  • Line number: 19533

Impact

Kubernetes will not be able to detect if application is able to service requests, and will not restart unhealthy pods

Remediation

Add `livenessProbe` attribute


Container is running without liveness probe

low severity

  • Public ID: SNYK-CC-K8S-41
  • Introduced through: [DocId: 45] spec template spec initContainers[copyutil] livenessProbe
  • Line number: 19790

Impact

Kubernetes will not be able to detect if application is able to service requests, and will not restart unhealthy pods

Remediation

Add `livenessProbe` attribute


Container is running without memory limit

low severity

  • Public ID: SNYK-CC-K8S-4
  • Introduced through: [DocId: 41] input spec template spec containers[argocd-applicationset-controller] resources limits memory
  • Line number: 19141

Impact

Containers without memory limits are more likely to be terminated when the node runs out of memory

Remediation

Set `resources.limits.memory` value


Container is running without memory limit

low severity

  • Public ID: SNYK-CC-K8S-4
  • Introduced through: [DocId: 42] input spec template spec containers[dex] resources limits memory
  • Line number: 19352

Impact

Containers without memory limits are more likely to be terminated when the node runs out of memory

Remediation

Set `resources.limits.memory` value


Container is running without memory limit

low severity

  • Public ID: SNYK-CC-K8S-4
  • Introduced through: [DocId: 42] input spec template spec initContainers[copyutil] resources limits memory
  • Line number: 19386

Impact

Containers without memory limits are more likely to be terminated when the node runs out of memory

Remediation

Set `resources.limits.memory` value


Container is running without memory limit

low severity

  • Public ID: SNYK-CC-K8S-4
  • Introduced through: [DocId: 43] input spec template spec containers[argocd-notifications-controller] resources limits memory
  • Line number: 19446

Impact

Containers without memory limits are more likely to be terminated when the node runs out of memory

Remediation

Set `resources.limits.memory` value


Container is running without memory limit

low severity

  • Public ID: SNYK-CC-K8S-4
  • Introduced through: [DocId: 44] input spec template spec containers[redis] resources limits memory
  • Line number: 19533

Impact

Containers without memory limits are more likely to be terminated when the node runs out of memory

Remediation

Set `resources.limits.memory` value


Container is running without memory limit

low severity

  • Public ID: SNYK-CC-K8S-4
  • Introduced through: [DocId: 45] input spec template spec initContainers[copyutil] resources limits memory
  • Line number: 19790

Impact

Containers without memory limits are more likely to be terminated when the node runs out of memory

Remediation

Set `resources.limits.memory` value


Container is running without memory limit

low severity

  • Public ID: SNYK-CC-K8S-4
  • Introduced through: [DocId: 45] input spec template spec containers[argocd-repo-server] resources limits memory
  • Line number: 19590

Impact

Containers without memory limits are more likely to be terminated when the node runs out of memory

Remediation

Set `resources.limits.memory` value


Container is running without memory limit

low severity

  • Public ID: SNYK-CC-K8S-4
  • Introduced through: [DocId: 46] input spec template spec containers[argocd-server] resources limits memory
  • Line number: 19875

Impact

Containers without memory limits are more likely to be terminated when the node runs out of memory

Remediation

Set `resources.limits.memory` value


Container is running without memory limit

low severity

  • Public ID: SNYK-CC-K8S-4
  • Introduced through: [DocId: 47] input spec template spec containers[argocd-application-controller] resources limits memory
  • Line number: 20191

Impact

Containers without memory limits are more likely to be terminated when the node runs out of memory

Remediation

Set `resources.limits.memory` value


Container's or Pod's UID could clash with host's UID

low severity

  • Public ID: SNYK-CC-K8S-11
  • Introduced through: [DocId: 41] input spec template spec containers[argocd-applicationset-controller] securityContext runAsUser
  • Line number: 19276

Impact

UID of the container processes could clash with host's UIDs and lead to unintentional authorization bypass

Remediation

Set `securityContext.runAsUser` value to greater or equal than 10'000. SecurityContext can be set on both `pod` and `container` level. If both are set, then the container level takes precedence


Container's or Pod's UID could clash with host's UID

low severity

  • Public ID: SNYK-CC-K8S-11
  • Introduced through: [DocId: 42] input spec template spec initContainers[copyutil] securityContext runAsUser
  • Line number: 19394

Impact

UID of the container processes could clash with host's UIDs and lead to unintentional authorization bypass

Remediation

Set `securityContext.runAsUser` value to greater or equal than 10'000. SecurityContext can be set on both `pod` and `container` level. If both are set, then the container level takes precedence


Container's or Pod's UID could clash with host's UID

low severity

  • Public ID: SNYK-CC-K8S-11
  • Introduced through: [DocId: 42] input spec template spec containers[dex] securityContext runAsUser
  • Line number: 19369

Impact

UID of the container processes could clash with host's UIDs and lead to unintentional authorization bypass

Remediation

Set `securityContext.runAsUser` value to greater or equal than 10'000. SecurityContext can be set on both `pod` and `container` level. If both are set, then the container level takes precedence


Container's or Pod's UID could clash with host's UID

low severity

  • Public ID: SNYK-CC-K8S-11
  • Introduced through: [DocId: 43] input spec template spec containers[argocd-notifications-controller] securityContext runAsUser
  • Line number: 19467

Impact

UID of the container processes could clash with host's UIDs and lead to unintentional authorization bypass

Remediation

Set `securityContext.runAsUser` value to greater or equal than 10'000. SecurityContext can be set on both `pod` and `container` level. If both are set, then the container level takes precedence


Container's or Pod's UID could clash with host's UID

low severity

  • Public ID: SNYK-CC-K8S-11
  • Introduced through: [DocId: 44] input spec template spec containers[redis] securityContext runAsUser
  • Line number: 19543

Impact

UID of the container processes could clash with host's UIDs and lead to unintentional authorization bypass

Remediation

Set `securityContext.runAsUser` value to greater or equal than 10'000. SecurityContext can be set on both `pod` and `container` level. If both are set, then the container level takes precedence


Container's or Pod's UID could clash with host's UID

low severity

  • Public ID: SNYK-CC-K8S-11
  • Introduced through: [DocId: 45] input spec template spec initContainers[copyutil] securityContext runAsUser
  • Line number: 19797

Impact

UID of the container processes could clash with host's UIDs and lead to unintentional authorization bypass

Remediation

Set `securityContext.runAsUser` value to greater or equal than 10'000. SecurityContext can be set on both `pod` and `container` level. If both are set, then the container level takes precedence


Container's or Pod's UID could clash with host's UID

low severity

  • Public ID: SNYK-CC-K8S-11
  • Introduced through: [DocId: 45] input spec template spec containers[argocd-repo-server] securityContext runAsUser
  • Line number: 19763

Impact

UID of the container processes could clash with host's UIDs and lead to unintentional authorization bypass

Remediation

Set `securityContext.runAsUser` value to greater or equal than 10'000. SecurityContext can be set on both `pod` and `container` level. If both are set, then the container level takes precedence


Container's or Pod's UID could clash with host's UID

low severity

  • Public ID: SNYK-CC-K8S-11
  • Introduced through: [DocId: 46] input spec template spec containers[argocd-server] securityContext runAsUser
  • Line number: 20101

Impact

UID of the container processes could clash with host's UIDs and lead to unintentional authorization bypass

Remediation

Set `securityContext.runAsUser` value to greater or equal than 10'000. SecurityContext can be set on both `pod` and `container` level. If both are set, then the container level takes precedence


Container's or Pod's UID could clash with host's UID

low severity

  • Public ID: SNYK-CC-K8S-11
  • Introduced through: [DocId: 47] input spec template spec containers[argocd-application-controller] securityContext runAsUser
  • Line number: 20339

Impact

UID of the container processes could clash with host's UIDs and lead to unintentional authorization bypass

Remediation

Set `securityContext.runAsUser` value to greater or equal than 10'000. SecurityContext can be set on both `pod` and `container` level. If both are set, then the container level takes precedence