929 KiB
929 KiB
| hide | |
|---|---|
|
Security Overview
Helm-Chart
Scan Results
Chart Object: inventree/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 'prepare' 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 'prepare' 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 'prepare' 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 'prepare' 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 'prepare' 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 'prepare' 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 'prepare' 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-inventree' of Deployment 'RELEASE-NAME-inventree' 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 'init-migrate' of Deployment 'RELEASE-NAME-inventree' 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 'nginx' of Deployment 'RELEASE-NAME-inventree' 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 'prepare' of Deployment 'RELEASE-NAME-inventree' 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 'worker' of Deployment 'RELEASE-NAME-inventree' 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-inventree' of Deployment 'RELEASE-NAME-inventree' 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 'init-migrate' of Deployment 'RELEASE-NAME-inventree' 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 'nginx' of Deployment 'RELEASE-NAME-inventree' 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 'prepare' of Deployment 'RELEASE-NAME-inventree' 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 'worker' of Deployment 'RELEASE-NAME-inventree' should add 'ALL' to 'securityContext.capabilities.drop' |
|
| Kubernetes Security Check | KSV011 | CPU not limited | LOW | Expand...Enforcing CPU limits prevents DoS via resource exhaustion.Container 'init-migrate' of Deployment 'RELEASE-NAME-inventree' should set 'resources.limits.cpu' |
|
| Kubernetes Security Check | KSV011 | CPU not limited | LOW | Expand...Enforcing CPU limits prevents DoS via resource exhaustion.Container 'nginx' of Deployment 'RELEASE-NAME-inventree' should set 'resources.limits.cpu' |
|
| Kubernetes Security Check | KSV011 | CPU not limited | LOW | Expand...Enforcing CPU limits prevents DoS via resource exhaustion.Container 'worker' of Deployment 'RELEASE-NAME-inventree' should set 'resources.limits.cpu' |
|
| 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 'init-migrate' of Deployment 'RELEASE-NAME-inventree' 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 'nginx' of Deployment 'RELEASE-NAME-inventree' 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 'prepare' of Deployment 'RELEASE-NAME-inventree' 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 'worker' of Deployment 'RELEASE-NAME-inventree' 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-inventree' of Deployment 'RELEASE-NAME-inventree' 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 'init-migrate' of Deployment 'RELEASE-NAME-inventree' 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 'nginx' of Deployment 'RELEASE-NAME-inventree' 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 'prepare' of Deployment 'RELEASE-NAME-inventree' 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 'worker' of Deployment 'RELEASE-NAME-inventree' should set 'securityContext.readOnlyRootFilesystem' to true |
|
| Kubernetes Security Check | KSV015 | CPU requests not specified | LOW | Expand...When containers have resource requests specified, the scheduler can make better decisions about which nodes to place pods on, and how to deal with resource contention.Container 'init-migrate' of Deployment 'RELEASE-NAME-inventree' should set 'resources.requests.cpu' |
|
| Kubernetes Security Check | KSV015 | CPU requests not specified | LOW | Expand...When containers have resource requests specified, the scheduler can make better decisions about which nodes to place pods on, and how to deal with resource contention.Container 'nginx' of Deployment 'RELEASE-NAME-inventree' should set 'resources.requests.cpu' |
|
| Kubernetes Security Check | KSV015 | CPU requests not specified | LOW | Expand...When containers have resource requests specified, the scheduler can make better decisions about which nodes to place pods on, and how to deal with resource contention.Container 'worker' of Deployment 'RELEASE-NAME-inventree' should set 'resources.requests.cpu' |
|
| Kubernetes Security Check | KSV016 | Memory requests not specified | LOW | Expand...When containers have memory requests specified, the scheduler can make better decisions about which nodes to place pods on, and how to deal with resource contention.Container 'init-migrate' of Deployment 'RELEASE-NAME-inventree' should set 'resources.requests.memory' |
|
| Kubernetes Security Check | KSV016 | Memory requests not specified | LOW | Expand...When containers have memory requests specified, the scheduler can make better decisions about which nodes to place pods on, and how to deal with resource contention.Container 'nginx' of Deployment 'RELEASE-NAME-inventree' should set 'resources.requests.memory' |
|
| Kubernetes Security Check | KSV016 | Memory requests not specified | LOW | Expand...When containers have memory requests specified, the scheduler can make better decisions about which nodes to place pods on, and how to deal with resource contention.Container 'worker' of Deployment 'RELEASE-NAME-inventree' should set 'resources.requests.memory' |
|
| 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 'prepare' of Deployment 'RELEASE-NAME-inventree' should set 'securityContext.privileged' to false |
|
| Kubernetes Security Check | KSV018 | Memory not limited | LOW | Expand...Enforcing memory limits prevents DoS via resource exhaustion.Container 'init-migrate' of Deployment 'RELEASE-NAME-inventree' should set 'resources.limits.memory' |
|
| Kubernetes Security Check | KSV018 | Memory not limited | LOW | Expand...Enforcing memory limits prevents DoS via resource exhaustion.Container 'nginx' of Deployment 'RELEASE-NAME-inventree' should set 'resources.limits.memory' |
|
| Kubernetes Security Check | KSV018 | Memory not limited | LOW | Expand...Enforcing memory limits prevents DoS via resource exhaustion.Container 'worker' of Deployment 'RELEASE-NAME-inventree' should set 'resources.limits.memory' |
|
| 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-inventree' of Deployment 'RELEASE-NAME-inventree' 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 'init-migrate' of Deployment 'RELEASE-NAME-inventree' 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 'nginx' of Deployment 'RELEASE-NAME-inventree' 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 'prepare' of Deployment 'RELEASE-NAME-inventree' 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 'worker' of Deployment 'RELEASE-NAME-inventree' 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-inventree' of Deployment 'RELEASE-NAME-inventree' 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 'init-migrate' of Deployment 'RELEASE-NAME-inventree' 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 'nginx' of Deployment 'RELEASE-NAME-inventree' 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 'prepare' of Deployment 'RELEASE-NAME-inventree' 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 'worker' of Deployment 'RELEASE-NAME-inventree' 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 | 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 |
|
| 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 |
|
| 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/multi-init:v0.0.1@sha256:41185dcea1e6f6a035d8090da40aecc6a69cef66b91dc1332a90c9d22861d367
'tccr.io/truecharts/inventree:v0.7.4@sha256:ac0be06d9e494ff08623a5b99e72f8ba0104d6259973bbcff74b571be36fc602'
tccr.io/truecharts/inventree:v0.7.4@sha256:ac0be06d9e494ff08623a5b99e72f8ba0104d6259973bbcff74b571be36fc602
- 'tccr.io/truecharts/nginx:v1.23.0@sha256:f4f43b06452c23534106d5dcebdff45fc7737ad360c6b84dda801d55d25548ea'
'tccr.io/truecharts/inventree:v0.7.4@sha256:ac0be06d9e494ff08623a5b99e72f8ba0104d6259973bbcff74b571be36fc602'
tccr.io/truecharts/multi-init:v0.0.1@sha256:41185dcea1e6f6a035d8090da40aecc6a69cef66b91dc1332a90c9d22861d367
tccr.io/truecharts/postgresql:v14.4.0@sha256:16f1954b5e3ca05d163c5d3c6edda0ec4e687cdd524133241df639f4423946dc
Scan Results
Container: tccr.io/truecharts/multi-init:v0.0.1@sha256:41185dcea1e6f6a035d8090da40aecc6a69cef66b91dc1332a90c9d22861d367 (ubuntu 20.04)
ubuntu
Container: tccr.io/truecharts/inventree:v0.7.4@sha256:ac0be06d9e494ff08623a5b99e72f8ba0104d6259973bbcff74b571be36fc602 (alpine 3.14.6)
alpine
node-pkg
| No Vulnerabilities found |
|---|
python-pkg
| Package | Vulnerability | Severity | Installed Version | Fixed Version | Links |
|---|---|---|---|---|---|
| Django | CVE-2022-34265 | CRITICAL | 3.2.13 | 3.2.14, 4.0.6 | Expand...https://access.redhat.com/security/cve/CVE-2022-34265https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-34265 https://docs.djangoproject.com/en/4.0/releases/security/ https://groups.google.com/forum/#!forum/django-announce https://ubuntu.com/security/notices/USN-5501-1 https://www.djangoproject.com/weblog/2022/jul/04/security-releases/ |
| Pillow | CVE-2022-30595 | HIGH | 9.1.0 | 9.1.1 | Expand...https://access.redhat.com/security/cve/CVE-2022-30595https://github.com/advisories/GHSA-hr8g-f6r6-mr22 https://github.com/python-pillow/Pillow/blob/main/src/libImaging/TgaRleDecode.c https://nvd.nist.gov/vuln/detail/CVE-2022-30595 https://pillow.readthedocs.io/en/stable/releasenotes/9.1.1.html |
| inventree | GHSA-85q9-7467-r53q | HIGH | 0.7.2 | 0.7.3 |
cargo
cargo
| Package | Vulnerability | Severity | Installed Version | Fixed Version | Links |
|---|---|---|---|---|---|
| cranelift-codegen | CVE-2021-32629 | HIGH | 0.70.0 | 0.73.1 | Expand...https://crates.io/crates/cranelift-codegenhttps://github.com/bytecodealliance/wasmtime/commit/95559c01aaa7c061088a433040f31e8291fb09d0 https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-hpqh-2wqx-7qp5 https://rustsec.org/advisories/RUSTSEC-2021-0067.html https://www.fastly.com/security-advisories/memory-access-due-to-code-generation-flaw-in-cranelift-module |
cargo
| Package | Vulnerability | Severity | Installed Version | Fixed Version | Links |
|---|---|---|---|---|---|
| term | RUSTSEC-2018-0015 | UNKNOWN | 0.0.0 | 0.6.2-0 |
| No Vulnerabilities found |
|---|
Container: tccr.io/truecharts/multi-init:v0.0.1@sha256:41185dcea1e6f6a035d8090da40aecc6a69cef66b91dc1332a90c9d22861d367 (ubuntu 20.04)
ubuntu
Container: tccr.io/truecharts/postgresql:v14.4.0@sha256:16f1954b5e3ca05d163c5d3c6edda0ec4e687cdd524133241df639f4423946dc (debian 11.3)
debian
jar
| No Vulnerabilities found |
|---|
gobinary