841 KiB
841 KiB
| hide | |
|---|---|
|
Security Overview
Helm-Chart
Scan Results
Chart Object: kutt/charts/postgresql/templates/common.yaml
| Type | Misconfiguration ID | Check | Severity | Explaination | Links |
|---|---|---|---|---|---|
| Kubernetes Security Check | KSV001 | Process can elevate its own privileges | MEDIUM | Expand...A program inside the container can elevate its own privileges and run as root, which might give the program control over the container and node.Container 'RELEASE-NAME-postgresql' of StatefulSet 'RELEASE-NAME-postgresql' should set 'securityContext.allowPrivilegeEscalation' to false |
|
| Kubernetes Security Check | KSV001 | Process can elevate its own privileges | MEDIUM | Expand...A program inside the container can elevate its own privileges and run as root, which might give the program control over the container and node.Container 'autopermissions' of StatefulSet 'RELEASE-NAME-postgresql' should set 'securityContext.allowPrivilegeEscalation' to false |
|
| Kubernetes Security Check | KSV003 | Default capabilities not dropped | LOW | Expand...The container should drop all default capabilities and add only those that are needed for its execution.Container 'RELEASE-NAME-postgresql' of StatefulSet 'RELEASE-NAME-postgresql' should add 'ALL' to 'securityContext.capabilities.drop' |
|
| Kubernetes Security Check | KSV003 | Default capabilities not dropped | LOW | Expand...The container should drop all default capabilities and add only those that are needed for its execution.Container 'autopermissions' of StatefulSet 'RELEASE-NAME-postgresql' should add 'ALL' to 'securityContext.capabilities.drop' |
|
| Kubernetes Security Check | KSV012 | Runs as root user | MEDIUM | Expand...'runAsNonRoot' forces the running image to run as a non-root user to ensure least privileges.Container 'autopermissions' of StatefulSet 'RELEASE-NAME-postgresql' should set 'securityContext.runAsNonRoot' to true |
|
| Kubernetes Security Check | KSV014 | Root file system is not read-only | LOW | Expand...An immutable root file system prevents applications from writing to their local disk. This can limit intrusions, as attackers will not be able to tamper with the file system or write foreign executables to disk.Container 'RELEASE-NAME-postgresql' of StatefulSet 'RELEASE-NAME-postgresql' should set 'securityContext.readOnlyRootFilesystem' to true |
|
| Kubernetes Security Check | KSV014 | Root file system is not read-only | LOW | Expand...An immutable root file system prevents applications from writing to their local disk. This can limit intrusions, as attackers will not be able to tamper with the file system or write foreign executables to disk.Container 'autopermissions' of StatefulSet 'RELEASE-NAME-postgresql' should set 'securityContext.readOnlyRootFilesystem' to true |
|
| Kubernetes Security Check | KSV017 | Privileged container | HIGH | Expand...Privileged containers share namespaces with the host system and do not offer any security. They should be used exclusively for system containers that require high privileges.Container 'autopermissions' of StatefulSet 'RELEASE-NAME-postgresql' should set 'securityContext.privileged' to false |
|
| Kubernetes Security Check | KSV020 | Runs with low user ID | LOW | Expand...Force the container to run with user ID > 10000 to avoid conflicts with the host’s user table.Container 'RELEASE-NAME-postgresql' of StatefulSet 'RELEASE-NAME-postgresql' should set 'securityContext.runAsUser' > 10000 |
|
| Kubernetes Security Check | KSV020 | Runs with low user ID | LOW | Expand...Force the container to run with user ID > 10000 to avoid conflicts with the host’s user table.Container 'autopermissions' of StatefulSet 'RELEASE-NAME-postgresql' should set 'securityContext.runAsUser' > 10000 |
|
| Kubernetes Security Check | KSV021 | Runs with low group ID | LOW | Expand...Force the container to run with group ID > 10000 to avoid conflicts with the host’s user table.Container 'RELEASE-NAME-postgresql' of StatefulSet 'RELEASE-NAME-postgresql' should set 'securityContext.runAsGroup' > 10000 |
|
| Kubernetes Security Check | KSV021 | Runs with low group ID | LOW | Expand...Force the container to run with group ID > 10000 to avoid conflicts with the host’s user table.Container 'autopermissions' of StatefulSet 'RELEASE-NAME-postgresql' should set 'securityContext.runAsGroup' > 10000 |
|
| Kubernetes Security Check | KSV030 | Default Seccomp profile not set | LOW | Expand...The RuntimeDefault/Localhost seccomp profile must be required, or allow specific additional profiles.Either Pod or Container should set 'securityContext.seccompProfile.type' to 'RuntimeDefault' |
|
| Kubernetes Security Check | KSV030 | Default Seccomp profile not set | LOW | Expand...The RuntimeDefault/Localhost seccomp profile must be required, or allow specific additional profiles.Either Pod or Container should set 'securityContext.seccompProfile.type' to 'RuntimeDefault' |
|
| Kubernetes Security Check | KSV105 | Containers must not set runAsUser to 0 | LOW | Expand...Containers should be forbidden from running with a root UID.securityContext.runAsUser should be set to a value greater than 0 |
|
| Kubernetes Security Check | KSV106 | Container capabilities must only include NET_BIND_SERVICE | LOW | Expand...Containers must drop ALL capabilities, and are only permitted to add back the NET_BIND_SERVICE capability.container should drop all |
|
| Kubernetes Security Check | KSV106 | Container capabilities must only include NET_BIND_SERVICE | LOW | Expand...Containers must drop ALL capabilities, and are only permitted to add back the NET_BIND_SERVICE capability.container should drop all |
| Type | Misconfiguration ID | Check | Severity | Explaination | Links |
|---|---|---|---|---|---|
| Kubernetes Security Check | KSV001 | Process can elevate its own privileges | MEDIUM | Expand...A program inside the container can elevate its own privileges and run as root, which might give the program control over the container and node.Container 'RELEASE-NAME-redis' of StatefulSet 'RELEASE-NAME-redis' should set 'securityContext.allowPrivilegeEscalation' to false |
|
| Kubernetes Security Check | KSV001 | Process can elevate its own privileges | MEDIUM | Expand...A program inside the container can elevate its own privileges and run as root, which might give the program control over the container and node.Container 'autopermissions' of StatefulSet 'RELEASE-NAME-redis' should set 'securityContext.allowPrivilegeEscalation' to false |
|
| Kubernetes Security Check | KSV003 | Default capabilities not dropped | LOW | Expand...The container should drop all default capabilities and add only those that are needed for its execution.Container 'RELEASE-NAME-redis' of StatefulSet 'RELEASE-NAME-redis' should add 'ALL' to 'securityContext.capabilities.drop' |
|
| Kubernetes Security Check | KSV003 | Default capabilities not dropped | LOW | Expand...The container should drop all default capabilities and add only those that are needed for its execution.Container 'autopermissions' of StatefulSet 'RELEASE-NAME-redis' should add 'ALL' to 'securityContext.capabilities.drop' |
|
| Kubernetes Security Check | KSV012 | Runs as root user | MEDIUM | Expand...'runAsNonRoot' forces the running image to run as a non-root user to ensure least privileges.Container 'autopermissions' of StatefulSet 'RELEASE-NAME-redis' should set 'securityContext.runAsNonRoot' to true |
|
| Kubernetes Security Check | KSV014 | Root file system is not read-only | LOW | Expand...An immutable root file system prevents applications from writing to their local disk. This can limit intrusions, as attackers will not be able to tamper with the file system or write foreign executables to disk.Container 'RELEASE-NAME-redis' of StatefulSet 'RELEASE-NAME-redis' should set 'securityContext.readOnlyRootFilesystem' to true |
|
| Kubernetes Security Check | KSV014 | Root file system is not read-only | LOW | Expand...An immutable root file system prevents applications from writing to their local disk. This can limit intrusions, as attackers will not be able to tamper with the file system or write foreign executables to disk.Container 'autopermissions' of StatefulSet 'RELEASE-NAME-redis' should set 'securityContext.readOnlyRootFilesystem' to true |
|
| Kubernetes Security Check | KSV017 | Privileged container | HIGH | Expand...Privileged containers share namespaces with the host system and do not offer any security. They should be used exclusively for system containers that require high privileges.Container 'autopermissions' of StatefulSet 'RELEASE-NAME-redis' should set 'securityContext.privileged' to false |
|
| Kubernetes Security Check | KSV020 | Runs with low user ID | LOW | Expand...Force the container to run with user ID > 10000 to avoid conflicts with the host’s user table.Container 'RELEASE-NAME-redis' of StatefulSet 'RELEASE-NAME-redis' should set 'securityContext.runAsUser' > 10000 |
|
| Kubernetes Security Check | KSV020 | Runs with low user ID | LOW | Expand...Force the container to run with user ID > 10000 to avoid conflicts with the host’s user table.Container 'autopermissions' of StatefulSet 'RELEASE-NAME-redis' should set 'securityContext.runAsUser' > 10000 |
|
| Kubernetes Security Check | KSV021 | Runs with low group ID | LOW | Expand...Force the container to run with group ID > 10000 to avoid conflicts with the host’s user table.Container 'RELEASE-NAME-redis' of StatefulSet 'RELEASE-NAME-redis' should set 'securityContext.runAsGroup' > 10000 |
|
| Kubernetes Security Check | KSV021 | Runs with low group ID | LOW | Expand...Force the container to run with group ID > 10000 to avoid conflicts with the host’s user table.Container 'autopermissions' of StatefulSet 'RELEASE-NAME-redis' should set 'securityContext.runAsGroup' > 10000 |
|
| Kubernetes Security Check | KSV030 | Default Seccomp profile not set | LOW | Expand...The RuntimeDefault/Localhost seccomp profile must be required, or allow specific additional profiles.Either Pod or Container should set 'securityContext.seccompProfile.type' to 'RuntimeDefault' |
|
| Kubernetes Security Check | KSV030 | Default Seccomp profile not set | LOW | Expand...The RuntimeDefault/Localhost seccomp profile must be required, or allow specific additional profiles.Either Pod or Container should set 'securityContext.seccompProfile.type' to 'RuntimeDefault' |
|
| Kubernetes Security Check | KSV105 | Containers must not set runAsUser to 0 | LOW | Expand...Containers should be forbidden from running with a root UID.securityContext.runAsUser should be set to a value greater than 0 |
|
| Kubernetes Security Check | KSV106 | Container capabilities must only include NET_BIND_SERVICE | LOW | Expand...Containers must drop ALL capabilities, and are only permitted to add back the NET_BIND_SERVICE capability.container should drop all |
|
| Kubernetes Security Check | KSV106 | Container capabilities must only include NET_BIND_SERVICE | LOW | Expand...Containers must drop ALL capabilities, and are only permitted to add back the NET_BIND_SERVICE capability.container should drop all |
| Type | Misconfiguration ID | Check | Severity | Explaination | Links |
|---|---|---|---|---|---|
| Kubernetes Security Check | KSV001 | Process can elevate its own privileges | MEDIUM | Expand...A program inside the container can elevate its own privileges and run as root, which might give the program control over the container and node.Container 'RELEASE-NAME-kutt' of Deployment 'RELEASE-NAME-kutt' should set 'securityContext.allowPrivilegeEscalation' to false |
|
| Kubernetes Security Check | KSV001 | Process can elevate its own privileges | MEDIUM | Expand...A program inside the container can elevate its own privileges and run as root, which might give the program control over the container and node.Container 'autopermissions' of Deployment 'RELEASE-NAME-kutt' should set 'securityContext.allowPrivilegeEscalation' to false |
|
| Kubernetes Security Check | KSV001 | Process can elevate its own privileges | MEDIUM | Expand...A program inside the container can elevate its own privileges and run as root, which might give the program control over the container and node.Container 'postgresql-init' of Deployment 'RELEASE-NAME-kutt' should set 'securityContext.allowPrivilegeEscalation' to false |
|
| Kubernetes Security Check | KSV001 | Process can elevate its own privileges | MEDIUM | Expand...A program inside the container can elevate its own privileges and run as root, which might give the program control over the container and node.Container 'redis-init' of Deployment 'RELEASE-NAME-kutt' should set 'securityContext.allowPrivilegeEscalation' to false |
|
| Kubernetes Security Check | KSV003 | Default capabilities not dropped | LOW | Expand...The container should drop all default capabilities and add only those that are needed for its execution.Container 'RELEASE-NAME-kutt' of Deployment 'RELEASE-NAME-kutt' should add 'ALL' to 'securityContext.capabilities.drop' |
|
| Kubernetes Security Check | KSV003 | Default capabilities not dropped | LOW | Expand...The container should drop all default capabilities and add only those that are needed for its execution.Container 'autopermissions' of Deployment 'RELEASE-NAME-kutt' should add 'ALL' to 'securityContext.capabilities.drop' |
|
| Kubernetes Security Check | KSV012 | Runs as root user | MEDIUM | Expand...'runAsNonRoot' forces the running image to run as a non-root user to ensure least privileges.Container 'RELEASE-NAME-kutt' of Deployment 'RELEASE-NAME-kutt' should set 'securityContext.runAsNonRoot' to true |
|
| Kubernetes Security Check | KSV012 | Runs as root user | MEDIUM | Expand...'runAsNonRoot' forces the running image to run as a non-root user to ensure least privileges.Container 'autopermissions' of Deployment 'RELEASE-NAME-kutt' should set 'securityContext.runAsNonRoot' to true |
|
| Kubernetes Security Check | KSV012 | Runs as root user | MEDIUM | Expand...'runAsNonRoot' forces the running image to run as a non-root user to ensure least privileges.Container 'postgresql-init' of Deployment 'RELEASE-NAME-kutt' should set 'securityContext.runAsNonRoot' to true |
|
| Kubernetes Security Check | KSV012 | Runs as root user | MEDIUM | Expand...'runAsNonRoot' forces the running image to run as a non-root user to ensure least privileges.Container 'redis-init' of Deployment 'RELEASE-NAME-kutt' should set 'securityContext.runAsNonRoot' to true |
|
| Kubernetes Security Check | KSV014 | Root file system is not read-only | LOW | Expand...An immutable root file system prevents applications from writing to their local disk. This can limit intrusions, as attackers will not be able to tamper with the file system or write foreign executables to disk.Container 'RELEASE-NAME-kutt' of Deployment 'RELEASE-NAME-kutt' should set 'securityContext.readOnlyRootFilesystem' to true |
|
| Kubernetes Security Check | KSV014 | Root file system is not read-only | LOW | Expand...An immutable root file system prevents applications from writing to their local disk. This can limit intrusions, as attackers will not be able to tamper with the file system or write foreign executables to disk.Container 'autopermissions' of Deployment 'RELEASE-NAME-kutt' should set 'securityContext.readOnlyRootFilesystem' to true |
|
| Kubernetes Security Check | KSV014 | Root file system is not read-only | LOW | Expand...An immutable root file system prevents applications from writing to their local disk. This can limit intrusions, as attackers will not be able to tamper with the file system or write foreign executables to disk.Container 'postgresql-init' of Deployment 'RELEASE-NAME-kutt' should set 'securityContext.readOnlyRootFilesystem' to true |
|
| Kubernetes Security Check | KSV014 | Root file system is not read-only | LOW | Expand...An immutable root file system prevents applications from writing to their local disk. This can limit intrusions, as attackers will not be able to tamper with the file system or write foreign executables to disk.Container 'redis-init' of Deployment 'RELEASE-NAME-kutt' should set 'securityContext.readOnlyRootFilesystem' to true |
|
| Kubernetes Security Check | KSV017 | Privileged container | HIGH | Expand...Privileged containers share namespaces with the host system and do not offer any security. They should be used exclusively for system containers that require high privileges.Container 'autopermissions' of Deployment 'RELEASE-NAME-kutt' should set 'securityContext.privileged' to false |
|
| Kubernetes Security Check | KSV020 | Runs with low user ID | LOW | Expand...Force the container to run with user ID > 10000 to avoid conflicts with the host’s user table.Container 'RELEASE-NAME-kutt' of Deployment 'RELEASE-NAME-kutt' should set 'securityContext.runAsUser' > 10000 |
|
| Kubernetes Security Check | KSV020 | Runs with low user ID | LOW | Expand...Force the container to run with user ID > 10000 to avoid conflicts with the host’s user table.Container 'autopermissions' of Deployment 'RELEASE-NAME-kutt' should set 'securityContext.runAsUser' > 10000 |
|
| Kubernetes Security Check | KSV020 | Runs with low user ID | LOW | Expand...Force the container to run with user ID > 10000 to avoid conflicts with the host’s user table.Container 'postgresql-init' of Deployment 'RELEASE-NAME-kutt' should set 'securityContext.runAsUser' > 10000 |
|
| Kubernetes Security Check | KSV020 | Runs with low user ID | LOW | Expand...Force the container to run with user ID > 10000 to avoid conflicts with the host’s user table.Container 'redis-init' of Deployment 'RELEASE-NAME-kutt' should set 'securityContext.runAsUser' > 10000 |
|
| Kubernetes Security Check | KSV021 | Runs with low group ID | LOW | Expand...Force the container to run with group ID > 10000 to avoid conflicts with the host’s user table.Container 'RELEASE-NAME-kutt' of Deployment 'RELEASE-NAME-kutt' should set 'securityContext.runAsGroup' > 10000 |
|
| Kubernetes Security Check | KSV021 | Runs with low group ID | LOW | Expand...Force the container to run with group ID > 10000 to avoid conflicts with the host’s user table.Container 'autopermissions' of Deployment 'RELEASE-NAME-kutt' should set 'securityContext.runAsGroup' > 10000 |
|
| Kubernetes Security Check | KSV021 | Runs with low group ID | LOW | Expand...Force the container to run with group ID > 10000 to avoid conflicts with the host’s user table.Container 'postgresql-init' of Deployment 'RELEASE-NAME-kutt' should set 'securityContext.runAsGroup' > 10000 |
|
| Kubernetes Security Check | KSV021 | Runs with low group ID | LOW | Expand...Force the container to run with group ID > 10000 to avoid conflicts with the host’s user table.Container 'redis-init' of Deployment 'RELEASE-NAME-kutt' should set 'securityContext.runAsGroup' > 10000 |
|
| Kubernetes Security Check | KSV030 | Default Seccomp profile not set | LOW | Expand...The RuntimeDefault/Localhost seccomp profile must be required, or allow specific additional profiles.Either Pod or Container should set 'securityContext.seccompProfile.type' to 'RuntimeDefault' |
|
| Kubernetes Security Check | KSV030 | Default Seccomp profile not set | LOW | Expand...The RuntimeDefault/Localhost seccomp profile must be required, or allow specific additional profiles.Either Pod or Container should set 'securityContext.seccompProfile.type' to 'RuntimeDefault' |
|
| Kubernetes Security Check | KSV030 | Default Seccomp profile not set | LOW | Expand...The RuntimeDefault/Localhost seccomp profile must be required, or allow specific additional profiles.Either Pod or Container should set 'securityContext.seccompProfile.type' to 'RuntimeDefault' |
|
| Kubernetes Security Check | KSV030 | Default Seccomp profile not set | LOW | Expand...The RuntimeDefault/Localhost seccomp profile must be required, or allow specific additional profiles.Either Pod or Container should set 'securityContext.seccompProfile.type' to 'RuntimeDefault' |
|
| Kubernetes Security Check | KSV105 | Containers must not set runAsUser to 0 | LOW | Expand...Containers should be forbidden from running with a root UID.securityContext.runAsUser should be set to a value greater than 0 |
|
| Kubernetes Security Check | KSV105 | Containers must not set runAsUser to 0 | LOW | Expand...Containers should be forbidden from running with a root UID.securityContext.runAsUser should be set to a value greater than 0 |
|
| Kubernetes Security Check | KSV106 | Container capabilities must only include NET_BIND_SERVICE | LOW | Expand...Containers must drop ALL capabilities, and are only permitted to add back the NET_BIND_SERVICE capability.container should drop all |
|
| Kubernetes Security Check | KSV106 | Container capabilities must only include NET_BIND_SERVICE | LOW | Expand...Containers must drop ALL capabilities, and are only permitted to add back the NET_BIND_SERVICE capability.container should drop all |
Containers
Detected Containers
tccr.io/truecharts/alpine:v3.16.0@sha256:16dc15f3d61a1e30b1df9f839e53636847b6097286b2b74c637b25fd8264f730
tccr.io/truecharts/postgresql:v14.4.0@sha256:9f88fe352b51208f9a8fa01a95c07a74751e72629d009230cfe18a427e30550c
tccr.io/truecharts/redis:v7.0.2@sha256:dfca138f71f1896a07b5ca1e6af88625824925bbbd7719a7676ac11e9e076661
tccr.io/truecharts/kutt:v2.7.4@sha256:7b89481d467e1c1dc75e672bdac18dd00fdb4a3f0b60d90518acbf8eddfe8615
tccr.io/truecharts/alpine:v3.16.0@sha256:16dc15f3d61a1e30b1df9f839e53636847b6097286b2b74c637b25fd8264f730
tccr.io/truecharts/postgresql:v14.4.0@sha256:9f88fe352b51208f9a8fa01a95c07a74751e72629d009230cfe18a427e30550c
tccr.io/truecharts/alpine:v3.16.0@sha256:16dc15f3d61a1e30b1df9f839e53636847b6097286b2b74c637b25fd8264f730
tccr.io/truecharts/redis:v7.0.2@sha256:55f0a77f91b8d51e8138d305019bdc17911d988c85b89fe901a456daa448f176
Scan Results
Container: tccr.io/truecharts/alpine:v3.16.0@sha256:16dc15f3d61a1e30b1df9f839e53636847b6097286b2b74c637b25fd8264f730 (alpine 3.16.0)
alpine
| No Vulnerabilities found |
|---|
Container: tccr.io/truecharts/postgresql:v14.4.0@sha256:9f88fe352b51208f9a8fa01a95c07a74751e72629d009230cfe18a427e30550c (debian 11.3)
debian
jar
| No Vulnerabilities found |
|---|
gobinary
Container: tccr.io/truecharts/redis:v7.0.2@sha256:dfca138f71f1896a07b5ca1e6af88625824925bbbd7719a7676ac11e9e076661 (debian 11.3)
debian
gobinary
gobinary
| No Vulnerabilities found |
|---|
Container: tccr.io/truecharts/kutt:v2.7.4@sha256:7b89481d467e1c1dc75e672bdac18dd00fdb4a3f0b60d90518acbf8eddfe8615 (alpine 3.15.0)
alpine
node-pkg
Container: tccr.io/truecharts/alpine:v3.16.0@sha256:16dc15f3d61a1e30b1df9f839e53636847b6097286b2b74c637b25fd8264f730 (alpine 3.16.0)
alpine
| No Vulnerabilities found |
|---|
Container: tccr.io/truecharts/postgresql:v14.4.0@sha256:9f88fe352b51208f9a8fa01a95c07a74751e72629d009230cfe18a427e30550c (debian 11.3)
debian
jar
| No Vulnerabilities found |
|---|
gobinary
Container: tccr.io/truecharts/alpine:v3.16.0@sha256:16dc15f3d61a1e30b1df9f839e53636847b6097286b2b74c637b25fd8264f730 (alpine 3.16.0)
alpine
| No Vulnerabilities found |
|---|
Container: tccr.io/truecharts/redis:v7.0.2@sha256:55f0a77f91b8d51e8138d305019bdc17911d988c85b89fe901a456daa448f176 (debian 11.3)
debian
gobinary
gobinary
| No Vulnerabilities found |
|---|