602 KiB
602 KiB
| hide | |
|---|---|
|
Security Overview
Helm-Chart
Scan Results
Chart Object: statping/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 '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 | MEDIUM | 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 | MEDIUM | 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 | MEDIUM | 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 | MEDIUM | 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 | KSV029 | A root primary or supplementary GID set | LOW | Expand...Containers should be forbidden from running with a root primary or supplementary GID.StatefulSet 'RELEASE-NAME-postgresql' should set 'spec.securityContext.runAsGroup', 'spec.securityContext.supplementalGroups[*]' and 'spec.securityContext.fsGroup' to integer greater than 0 |
| 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 'autopermissions' of Deployment 'RELEASE-NAME-statping' 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-statping' 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-statping' of Deployment 'RELEASE-NAME-statping' 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-statping' 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 Deployment 'RELEASE-NAME-statping' 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-statping' 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 'autopermissions' of Deployment 'RELEASE-NAME-statping' 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-statping' 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-statping' should set 'securityContext.privileged' to false |
|
| Kubernetes Security Check | KSV020 | Runs with low user ID | MEDIUM | Expand...Force the container to run with user ID > 10000 to avoid conflicts with the host’s user table.Container 'RELEASE-NAME-statping' of Deployment 'RELEASE-NAME-statping' should set 'securityContext.runAsUser' > 10000 |
|
| Kubernetes Security Check | KSV020 | Runs with low user ID | MEDIUM | 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-statping' should set 'securityContext.runAsUser' > 10000 |
|
| Kubernetes Security Check | KSV020 | Runs with low user ID | MEDIUM | 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-statping' should set 'securityContext.runAsUser' > 10000 |
|
| Kubernetes Security Check | KSV021 | Runs with low group ID | MEDIUM | Expand...Force the container to run with group ID > 10000 to avoid conflicts with the host’s user table.Container 'RELEASE-NAME-statping' of Deployment 'RELEASE-NAME-statping' should set 'securityContext.runAsGroup' > 10000 |
|
| Kubernetes Security Check | KSV021 | Runs with low group ID | MEDIUM | 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-statping' should set 'securityContext.runAsGroup' > 10000 |
|
| Kubernetes Security Check | KSV021 | Runs with low group ID | MEDIUM | 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-statping' should set 'securityContext.runAsGroup' > 10000 |
|
| Kubernetes Security Check | KSV029 | A root primary or supplementary GID set | LOW | Expand...Containers should be forbidden from running with a root primary or supplementary GID.Deployment 'RELEASE-NAME-statping' should set 'spec.securityContext.runAsGroup', 'spec.securityContext.supplementalGroups[*]' and 'spec.securityContext.fsGroup' to integer greater than 0 |
Containers
Detected Containers
tccr.io/truecharts/alpine:v3.15.2@sha256:29ed3480a0ee43f7af681fed5d4fc215516abf1c41eade6938b26d8c9c2c7583
tccr.io/truecharts/postgresql:v14.3.0@sha256:8ceb5ef6482804203d3b09251df17c9b202ac29e4292c6cb6559db93ca57dfc3
tccr.io/truecharts/alpine:v3.15.2@sha256:29ed3480a0ee43f7af681fed5d4fc215516abf1c41eade6938b26d8c9c2c7583
tccr.io/truecharts/postgresql:v14.3.0@sha256:997205be58254e4196f4afdf2d0f539b809177966f62cc9891cca037b3da37a7
tccr.io/truecharts/statping:v0.90.78@sha256:975e6f7361c435414d14c3700a356819fd6f4eb00df8cb2c13a24e5511580042
Scan Results
Container: tccr.io/truecharts/alpine:v3.15.2@sha256:29ed3480a0ee43f7af681fed5d4fc215516abf1c41eade6938b26d8c9c2c7583 (alpine 3.15.2)
alpine
Container: tccr.io/truecharts/postgresql:v14.3.0@sha256:8ceb5ef6482804203d3b09251df17c9b202ac29e4292c6cb6559db93ca57dfc3 (debian 11.3)
debian
jar
| No Vulnerabilities found |
|---|
gobinary
Container: tccr.io/truecharts/alpine:v3.15.2@sha256:29ed3480a0ee43f7af681fed5d4fc215516abf1c41eade6938b26d8c9c2c7583 (alpine 3.15.2)
alpine
Container: tccr.io/truecharts/postgresql:v14.3.0@sha256:997205be58254e4196f4afdf2d0f539b809177966f62cc9891cca037b3da37a7 (debian 10.12)
debian
jar
| No Vulnerabilities found |
|---|
gobinary
Container: tccr.io/truecharts/statping:v0.90.78@sha256:975e6f7361c435414d14c3700a356819fd6f4eb00df8cb2c13a24e5511580042 (alpine 3.14.2)
alpine
gobinary
| Package | Vulnerability | Severity | Installed Version | Fixed Version | Links |
|---|---|---|---|---|---|
| github.com/dgrijalva/jwt-go | CVE-2020-26160 | HIGH | v3.2.0+incompatible | Expand...https://access.redhat.com/security/cve/CVE-2020-26160https://github.com/dgrijalva/jwt-go/commit/ec0a89a131e3e8567adcb21254a5cd20a70ea4ab https://github.com/dgrijalva/jwt-go/issues/422 https://github.com/dgrijalva/jwt-go/pull/426 https://nvd.nist.gov/vuln/detail/CVE-2020-26160 https://pkg.go.dev/vuln/GO-2020-0017 https://snyk.io/vuln/SNYK-GOLANG-GITHUBCOMDGRIJALVAJWTGO-596515 |
|
| golang.org/x/text | CVE-2021-38561 | UNKNOWN | v0.3.3 | 0.3.7 |