Repository scan
Fixops
DevOpsMadDog/Fixops · branch main · scanned 25 Jun 2026 · 320 resources
High 149
High 49 known vulnerabilities in unknown@unknown (dependencytrack/frontend:4.12.3)
How to fix
No fixed version of unknown is available yet. Check whether dependencytrack/frontend:4.12.3 needs unknown at all (a slimmer or distroless base image often drops it), watch the advisory for a fix, or accept the risk with a review date if it isn't reachable in your setup.
Vulnerabilities
- High CVE-2026-44495 fixed in no fix yet
- High CVE-2026-42043 fixed in no fix yet
- High CVE-2026-42033 fixed in no fix yet
- High CVE-2026-42035 fixed in no fix yet
- High CVE-2026-42264 fixed in no fix yet
- High CVE-2025-58754 fixed in no fix yet
- High CVE-2026-25639 fixed in no fix yet
- High CVE-2026-44486 fixed in no fix yet
- High CVE-2026-44488 fixed in no fix yet
- High CVE-2026-44496 fixed in no fix yet
- High CVE-2025-27152 fixed in no fix yet
- High CVE-2026-4800 fixed in no fix yet
- High CVE-2026-44487 fixed in no fix yet
- High CVE-2026-44492 fixed in no fix yet
- High CVE-2026-44494 fixed in no fix yet
- Medium CVE-2025-26791 fixed in no fix yet
- Medium CVE-2025-64758 fixed in no fix yet
- Medium CVE-2026-40175 fixed in no fix yet
- Medium CVE-2026-42041 fixed in no fix yet
- Medium CVE-2026-44490 fixed in no fix yet
- and 29 more
High 26 known vulnerabilities in curl@8.11.1-r0 (dependencytrack/frontend:4.12.3)
How to fix
Update curl from 8.11.1-r0 to 8.12.0-r0 or later in dependencytrack/frontend:4.12.3. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 8.12.0-r0); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- High CVE-2025-0665 fixed in 8.12.0-r0
- High CVE-2025-0725 fixed in 8.12.0-r0
- High CVE-2025-5399 fixed in 8.14.1-r0
- High CVE-2025-9086 fixed in 8.14.1-r2
- High CVE-2026-3805 fixed in no fix yet
- High CVE-2026-5773 fixed in no fix yet
- High CVE-2026-6276 fixed in no fix yet
- Medium CVE-2025-10966 fixed in no fix yet
- Medium CVE-2025-5025 fixed in 8.14.0-r0
- Medium CVE-2025-10148 fixed in 8.14.1-r2
- Medium CVE-2025-14524 fixed in no fix yet
- Medium CVE-2025-14819 fixed in no fix yet
- Medium CVE-2025-15079 fixed in no fix yet
- Medium CVE-2026-3783 fixed in no fix yet
- Medium CVE-2026-6429 fixed in no fix yet
- Medium CVE-2026-7168 fixed in no fix yet
- Medium CVE-2025-13034 fixed in no fix yet
- Medium CVE-2026-4873 fixed in no fix yet
- Medium CVE-2026-6253 fixed in no fix yet
- Medium CVE-2025-14017 fixed in no fix yet
- and 6 more
High 21 known vulnerabilities in openssl@3.3.2-r1 (dependencytrack/frontend:4.12.3)
How to fix
Update openssl from 3.3.2-r1 to 3.3.6-r0 or later in dependencytrack/frontend:4.12.3. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 3.3.6-r0); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- High CVE-2025-69419 fixed in 3.3.6-r0
- High CVE-2025-69420 fixed in 3.3.6-r0
- High CVE-2025-69421 fixed in 3.3.6-r0
- High CVE-2025-9230 fixed in 3.3.5-r0
- High CVE-2026-28388 fixed in 3.3.7-r0
- High CVE-2026-28389 fixed in 3.3.7-r0
- High CVE-2026-28390 fixed in 3.3.7-r0
- High CVE-2026-31790 fixed in 3.3.7-r0
- High CVE-2026-28387 fixed in 3.3.7-r0
- High CVE-2025-15467 fixed in 3.3.6-r0
- High CVE-2026-31789 fixed in 3.3.7-r0
- Medium CVE-2025-69418 fixed in 3.3.6-r0
- Medium CVE-2024-13176 fixed in 3.3.2-r2
- Medium CVE-2025-68160 fixed in 3.3.6-r0
- Medium CVE-2026-22796 fixed in 3.3.6-r0
- Medium CVE-2026-22795 fixed in 3.3.6-r0
- Medium CVE-2025-15468 fixed in 3.3.6-r0
- Medium CVE-2025-66199 fixed in 3.3.6-r0
- Medium CVE-2025-9232 fixed in 3.3.5-r0
- Medium CVE-2024-12797 fixed in 3.3.3-r0
- and 1 more
High 14 known vulnerabilities in jq@1.7.1-r0 (dependencytrack/frontend:4.12.3)
How to fix
No fixed version of jq is available yet. Check whether dependencytrack/frontend:4.12.3 needs jq at all (a slimmer or distroless base image often drops it), watch the advisory for a fix, or accept the risk with a review date if it isn't reachable in your setup.
Vulnerabilities
- High CVE-2025-48060 fixed in no fix yet
- High CVE-2024-53427 fixed in no fix yet
- High CVE-2026-32316 fixed in no fix yet
- Medium CVE-2024-23337 fixed in no fix yet
- Medium CVE-2026-43895 fixed in no fix yet
- Medium CVE-2026-40612 fixed in no fix yet
- Medium CVE-2026-44777 fixed in no fix yet
- Medium CVE-2026-41256 fixed in no fix yet
- Medium CVE-2026-33947 fixed in no fix yet
- Medium CVE-2026-43894 fixed in no fix yet
- Medium CVE-2026-43896 fixed in no fix yet
- Medium CVE-2026-41257 fixed in no fix yet
- Medium CVE-2026-39979 fixed in no fix yet
- Low CVE-2026-33948 fixed in no fix yet
High 11 known vulnerabilities in libpng@1.6.44-r0 (dependencytrack/frontend:4.12.3)
How to fix
Update libpng from 1.6.44-r0 to 1.6.53-r0 or later in dependencytrack/frontend:4.12.3. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 1.6.53-r0); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- High CVE-2025-64720 fixed in 1.6.53-r0
- High CVE-2025-65018 fixed in 1.6.53-r0
- High CVE-2025-66293 fixed in 1.6.53-r0
- High CVE-2026-33416 fixed in 1.6.56-r0
- High CVE-2026-33636 fixed in 1.6.56-r0
- High CVE-2026-25646 fixed in 1.6.55-r0
- Medium CVE-2026-34757 fixed in 1.6.57-r0
- Medium CVE-2025-64505 fixed in 1.6.53-r0
- Medium CVE-2025-64506 fixed in 1.6.53-r0
- Medium CVE-2026-22695 fixed in 1.6.54-r0
- Medium CVE-2026-22801 fixed in 1.6.54-r0
High 10 known vulnerabilities in expat@2.6.4-r0 (dependencytrack/frontend:4.12.3)
How to fix
Update expat from 2.6.4-r0 to 2.7.0-r0 or later in dependencytrack/frontend:4.12.3. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 2.7.0-r0); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- High CVE-2024-8176 fixed in 2.7.0-r0
- High CVE-2025-59375 fixed in 2.7.2-r0
- High CVE-2026-32767 fixed in 2.7.5-r0
- Medium CVE-2026-32776 fixed in 2.7.5-r0
- Medium CVE-2026-32777 fixed in 2.7.5-r0
- Medium CVE-2026-25210 fixed in 2.7.4-r0
- Low CVE-2026-24515 fixed in 2.7.4-r0
- Low CVE-2026-32778 fixed in 2.7.5-r0
- Low CVE-2026-41080 fixed in 2.8.1-r0
- Low CVE-2026-45186 fixed in 2.8.1-r0
High 6 known vulnerabilities in libxml2@2.12.7-r0 (dependencytrack/frontend:4.12.3)
How to fix
No fixed version of libxml2 is available yet. Check whether dependencytrack/frontend:4.12.3 needs libxml2 at all (a slimmer or distroless base image often drops it), watch the advisory for a fix, or accept the risk with a review date if it isn't reachable in your setup.
Vulnerabilities
- High CVE-2025-6021 fixed in no fix yet
- High CVE-2024-56171 fixed in 2.12.7-r1
- High CVE-2025-24928 fixed in 2.12.7-r1
- Medium CVE-2025-32414 fixed in 2.12.10-r0
- Low CVE-2025-27113 fixed in 2.12.7-r2
- Low CVE-2025-32415 fixed in 2.12.10-r0
High 3 known vulnerabilities in musl@1.2.5-r0 (dependencytrack/frontend:4.12.3)
How to fix
Update musl from 1.2.5-r0 to 1.2.5-r1 or later in dependencytrack/frontend:4.12.3. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 1.2.5-r1); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- High CVE-2025-26519 fixed in 1.2.5-r1
- High CVE-2026-40200 fixed in 1.2.5-r3
- Medium CVE-2026-6042 fixed in 1.2.5-r2
High 2 known vulnerabilities in c-ares@1.33.1-r0 (dependencytrack/frontend:4.12.3)
How to fix
No fixed version of c-ares is available yet. Check whether dependencytrack/frontend:4.12.3 needs c-ares at all (a slimmer or distroless base image often drops it), watch the advisory for a fix, or accept the risk with a review date if it isn't reachable in your setup.
Vulnerabilities
- High CVE-2025-31498 fixed in no fix yet
- Medium CVE-2025-62408 fixed in no fix yet
High 2 known vulnerabilities in libxslt@1.1.39-r1 (dependencytrack/frontend:4.12.3)
How to fix
Update libxslt from 1.1.39-r1 to 1.1.39-r2 or later in dependencytrack/frontend:4.12.3. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 1.1.39-r2); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- High CVE-2024-55549 fixed in 1.1.39-r2
- High CVE-2025-24855 fixed in 1.1.39-r2
High 2 known vulnerabilities in xz@5.6.2-r0 (dependencytrack/frontend:4.12.3)
How to fix
Update xz from 5.6.2-r0 to 5.6.2-r1 or later in dependencytrack/frontend:4.12.3. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 5.6.2-r1); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- High CVE-2025-31115 fixed in 5.6.2-r1
- Low CVE-2026-34743 fixed in 5.8.3-r0
High Expensive NAT Gateway
NAT Gateways are expensive managed services. Ensure they are strictly necessary.
How to fix
Consider using VPC Endpoints, NAT Instances for non-critical workloads, or share a single NAT Gateway across multiple subnets.
Where
High 1 known vulnerability in nghttp2@1.62.1-r0 (dependencytrack/frontend:4.12.3)
How to fix
No fixed version of nghttp2 is available yet. Check whether dependencytrack/frontend:4.12.3 needs nghttp2 at all (a slimmer or distroless base image often drops it), watch the advisory for a fix, or accept the risk with a review date if it isn't reachable in your setup.
Vulnerabilities
- High CVE-2026-27135 fixed in no fix yet
Medium 356
Medium Image should use digest
Image should use digest
Where
- ../../suite-core/config/deployment-packs/aws/terraform/main.tf:393
- ../../suite-core/config/deployment-packs/azure/terraform/main.tf:222
- ../../suite-core/config/deployment-packs/gcp/terraform/main.tf:302
- ../../suite-core/config/terraform/enterprise/modules/backend/main.tf:42
- ../../suite-core/telemetry_bridge/edge_collector/gcp/main.tf:131
- ../../suite-core/config/deployment-packs/kubernetes/manifests/redis-deployment.yaml:1
- ../../suite-core/config/deployment-packs/kubernetes/manifests/backend-deployment.yaml:1
- ../../suite-core/config/deployment-packs/kubernetes/manifests/mongodb-deployment.yaml:1
- ../../suite-core/config/kubernetes/enterprise/frontend-deployment.yaml:1
- ../../suite-core/config/kubernetes/enterprise/backend-deployment.yaml:1
- ../../tests/fixtures/k8s_manifests/workload.yaml:8
- ../../tests/fixtures/k8s_manifests/workload.yaml:34
- ../../docker/kubernetes/api-deployment.yaml:1
- ../../docker/kubernetes/ui-deployment.yaml:1
- ../../docker/kubernetes/cronjob-backup.yaml:1
Medium Minimize the admission of containers with the NET_RAW capability
Minimize the admission of containers with the NET_RAW capability
Where
- ../../suite-core/config/deployment-packs/aws/terraform/main.tf:393
- ../../suite-core/config/deployment-packs/azure/terraform/main.tf:222
- ../../suite-core/config/deployment-packs/gcp/terraform/main.tf:302
- ../../suite-core/config/terraform/enterprise/modules/backend/main.tf:42
- ../../suite-core/telemetry_bridge/edge_collector/gcp/main.tf:131
- ../../suite-core/config/deployment-packs/kubernetes/manifests/redis-deployment.yaml:1
- ../../suite-core/config/deployment-packs/kubernetes/manifests/backend-deployment.yaml:1
- ../../suite-core/config/deployment-packs/kubernetes/manifests/mongodb-deployment.yaml:1
- ../../suite-core/config/kubernetes/enterprise/frontend-deployment.yaml:1
- ../../suite-core/config/kubernetes/enterprise/backend-deployment.yaml:1
- ../../tests/fixtures/k8s_manifests/workload.yaml:8
- ../../tests/fixtures/k8s_manifests/workload.yaml:34
Medium Image Tag should be fixed - not latest or blank
Image Tag should be fixed - not latest or blank
Where
- ../../suite-core/config/deployment-packs/azure/terraform/main.tf:222
- ../../suite-core/config/terraform/enterprise/modules/backend/main.tf:42
- ../../suite-core/telemetry_bridge/edge_collector/gcp/main.tf:131
- ../../suite-core/config/deployment-packs/kubernetes/manifests/backend-deployment.yaml:1
- ../../suite-core/config/kubernetes/enterprise/frontend-deployment.yaml:1
- ../../suite-core/config/kubernetes/enterprise/backend-deployment.yaml:1
- ../../tests/fixtures/k8s_manifests/workload.yaml:8
- ../../tests/fixtures/k8s_manifests/workload.yaml:34
- ../../docker/kubernetes/api-deployment.yaml:1
- ../../docker/kubernetes/ui-deployment.yaml:1
- ../../docker/kubernetes/cronjob-backup.yaml:1
Medium Base64 High Entropy String
Base64 High Entropy String
Where
- ../../docker/kubernetes/secrets.yaml:30
- ../../suite-core/config/deployment-packs/kubernetes/manifests/secret.yaml:12
- ../../suite-core/config/fixops.overlay.yml:555
- ../../suite-core/telemetry_bridge/edge_collector/aks/values.yaml:62
- ../../suite-core/telemetry_bridge/edge_collector/azure/main.bicep:314
- ../../suite-core/telemetry_bridge/edge_collector/azure/main.bicep:318
- ../../suite-integrations/backstage/enterprise/template.yaml:199
- ../../suite-integrations/backstage/enterprise/template.yaml:199
- ../../suite-integrations/backstage/enterprise/template.yaml:199
- ../../suite-integrations/postman/enterprise/ALdeci-Environment.postman_environment.json:13
- ../../tests/fixtures/archive_data/samples/api-examples/integrations/slack-integration.json:9
Medium Containers should run as a high UID to avoid host conflict
Containers should run as a high UID to avoid host conflict
Where
- ../../suite-core/config/deployment-packs/kubernetes/manifests/redis-deployment.yaml:1
- ../../suite-core/config/deployment-packs/kubernetes/manifests/backend-deployment.yaml:1
- ../../suite-core/config/deployment-packs/kubernetes/manifests/mongodb-deployment.yaml:1
- ../../suite-core/config/kubernetes/enterprise/frontend-deployment.yaml:1
- ../../suite-core/config/kubernetes/enterprise/backend-deployment.yaml:1
- ../../tests/fixtures/k8s_manifests/workload.yaml:8
- ../../tests/fixtures/k8s_manifests/workload.yaml:34
- ../../docker/kubernetes/api-deployment.yaml:1
- ../../docker/kubernetes/ui-deployment.yaml:1
- ../../docker/kubernetes/cronjob-backup.yaml:1
Medium Ensure that HEALTHCHECK instructions have been added to container images
Ensure that HEALTHCHECK instructions have been added to container images
Where
- ../../suite-core/telemetry_bridge/edge_collector/fluent-bit/Dockerfile:1
- ../../suite-integrations/gitlab-ci/Dockerfile:1
- ../../suite-ui/aldeci-ui-new/Dockerfile:1
- ../../suite-integrations/github-action/Dockerfile:1
- ../../suite-core/telemetry_bridge/edge_collector/collector_api/Dockerfile:1
- ../../suite-core/telemetry_bridge/edge_collector/vector/Dockerfile:1
- ../../suite-integrations/mpte-aldeci/Dockerfile:1
Medium Ensure that a user for the container has been created
Ensure that a user for the container has been created
Where
- ../../suite-core/telemetry_bridge/edge_collector/fluent-bit/Dockerfile:1
- ../../docker/Dockerfile.ui:1
- ../../suite-integrations/gitlab-ci/Dockerfile:1
- ../../suite-ui/aldeci-ui-new/Dockerfile:1
- ../../suite-integrations/github-action/Dockerfile:1
- ../../suite-core/telemetry_bridge/edge_collector/collector_api/Dockerfile:1
- ../../suite-core/telemetry_bridge/edge_collector/vector/Dockerfile:1
Medium Containers should not run with allowPrivilegeEscalation
Containers should not run with allowPrivilegeEscalation
Where
- ../../suite-core/config/deployment-packs/kubernetes/manifests/redis-deployment.yaml:1
- ../../suite-core/config/deployment-packs/kubernetes/manifests/backend-deployment.yaml:1
- ../../suite-core/config/deployment-packs/kubernetes/manifests/mongodb-deployment.yaml:1
- ../../suite-core/config/kubernetes/enterprise/frontend-deployment.yaml:1
- ../../suite-core/config/kubernetes/enterprise/backend-deployment.yaml:1
- ../../tests/fixtures/k8s_manifests/workload.yaml:8
- ../../tests/fixtures/k8s_manifests/workload.yaml:34
Medium Use read-only filesystem for containers where possible
Use read-only filesystem for containers where possible
Where
- ../../suite-core/config/deployment-packs/kubernetes/manifests/redis-deployment.yaml:1
- ../../suite-core/config/deployment-packs/kubernetes/manifests/backend-deployment.yaml:1
- ../../suite-core/config/deployment-packs/kubernetes/manifests/mongodb-deployment.yaml:1
- ../../suite-core/config/kubernetes/enterprise/frontend-deployment.yaml:1
- ../../suite-core/config/kubernetes/enterprise/backend-deployment.yaml:1
- ../../tests/fixtures/k8s_manifests/workload.yaml:8
- ../../tests/fixtures/k8s_manifests/workload.yaml:34
Medium Ensure that the seccomp profile is set to docker/default or runtime/default
Ensure that the seccomp profile is set to docker/default or runtime/default
Where
- ../../suite-core/config/deployment-packs/kubernetes/manifests/redis-deployment.yaml:1
- ../../suite-core/config/deployment-packs/kubernetes/manifests/backend-deployment.yaml:1
- ../../suite-core/config/deployment-packs/kubernetes/manifests/mongodb-deployment.yaml:1
- ../../suite-core/config/kubernetes/enterprise/frontend-deployment.yaml:1
- ../../suite-core/config/kubernetes/enterprise/backend-deployment.yaml:1
- ../../tests/fixtures/k8s_manifests/workload.yaml:8
- ../../tests/fixtures/k8s_manifests/workload.yaml:34
Medium Prefer using secrets as files over secrets as environment variables
Prefer using secrets as files over secrets as environment variables
Where
- ../../suite-core/config/deployment-packs/gcp/terraform/main.tf:302
- ../../suite-core/config/deployment-packs/kubernetes/manifests/redis-deployment.yaml:1
- ../../suite-core/config/deployment-packs/kubernetes/manifests/backend-deployment.yaml:1
- ../../suite-core/config/deployment-packs/kubernetes/manifests/mongodb-deployment.yaml:1
- ../../suite-core/config/kubernetes/enterprise/backend-deployment.yaml:1
- ../../docker/kubernetes/api-deployment.yaml:1
- ../../docker/kubernetes/cronjob-backup.yaml:1
Medium Minimize the admission of containers with capabilities assigned
Minimize the admission of containers with capabilities assigned
Where
- ../../suite-core/config/deployment-packs/kubernetes/manifests/redis-deployment.yaml:1
- ../../suite-core/config/deployment-packs/kubernetes/manifests/backend-deployment.yaml:1
- ../../suite-core/config/deployment-packs/kubernetes/manifests/mongodb-deployment.yaml:1
- ../../suite-core/config/kubernetes/enterprise/frontend-deployment.yaml:1
- ../../suite-core/config/kubernetes/enterprise/backend-deployment.yaml:1
- ../../tests/fixtures/k8s_manifests/workload.yaml:8
- ../../tests/fixtures/k8s_manifests/workload.yaml:34
Medium Ensure that Service Account Tokens are only mounted where necessary
Ensure that Service Account Tokens are only mounted where necessary
Where
- ../../suite-core/config/deployment-packs/kubernetes/manifests/redis-deployment.yaml:1
- ../../suite-core/config/deployment-packs/kubernetes/manifests/backend-deployment.yaml:1
- ../../suite-core/config/deployment-packs/kubernetes/manifests/mongodb-deployment.yaml:1
- ../../suite-core/config/kubernetes/enterprise/frontend-deployment.yaml:1
- ../../suite-core/config/kubernetes/enterprise/backend-deployment.yaml:1
- ../../tests/fixtures/k8s_manifests/workload.yaml:8
- ../../tests/fixtures/k8s_manifests/workload.yaml:34
Medium Ensure no security groups allow egress from 0.0.0.0:0 to port -1
Ensure no security groups allow egress from 0.0.0.0:0 to port -1
Where
Medium Ensure S3 buckets should have event notifications enabled
Ensure S3 buckets should have event notifications enabled
Where
Medium Ensure that S3 buckets are encrypted with KMS by default
Ensure that S3 buckets are encrypted with KMS by default
Where
Medium Ensure that CloudWatch Log Group is encrypted by KMS
Ensure that CloudWatch Log Group is encrypted by KMS
Where
Medium Ensure the S3 bucket has access logging enabled
Medium Image Pull Policy should be Always
Image Pull Policy should be Always
Where
- ../../suite-core/config/deployment-packs/aws/terraform/main.tf:393
- ../../suite-core/config/deployment-packs/gcp/terraform/main.tf:302
- ../../suite-core/config/deployment-packs/kubernetes/manifests/redis-deployment.yaml:1
- ../../suite-core/config/deployment-packs/kubernetes/manifests/mongodb-deployment.yaml:1
- ../../docker/kubernetes/cronjob-backup.yaml:1
Medium Minimize the admission of root containers
Minimize the admission of root containers
Where
- ../../suite-core/config/deployment-packs/kubernetes/manifests/redis-deployment.yaml:1
- ../../suite-core/config/deployment-packs/kubernetes/manifests/backend-deployment.yaml:1
- ../../suite-core/config/deployment-packs/kubernetes/manifests/mongodb-deployment.yaml:1
- ../../tests/fixtures/k8s_manifests/workload.yaml:8
- ../../tests/fixtures/k8s_manifests/workload.yaml:34
Medium Apply security context to your pods and containers
Apply security context to your pods and containers
Where
- ../../suite-core/config/deployment-packs/kubernetes/manifests/redis-deployment.yaml:1
- ../../suite-core/config/deployment-packs/kubernetes/manifests/backend-deployment.yaml:1
- ../../suite-core/config/deployment-packs/kubernetes/manifests/mongodb-deployment.yaml:1
- ../../tests/fixtures/k8s_manifests/workload.yaml:8
- ../../tests/fixtures/k8s_manifests/workload.yaml:34
Medium Apply security context to your pods, deployments and daemon_sets
Apply security context to your pods, deployments and daemon_sets
Where
- ../../suite-core/config/deployment-packs/aws/terraform/main.tf:393
- ../../suite-core/config/deployment-packs/azure/terraform/main.tf:222
- ../../suite-core/config/deployment-packs/gcp/terraform/main.tf:302
- ../../suite-core/config/terraform/enterprise/modules/backend/main.tf:42
- ../../suite-core/telemetry_bridge/edge_collector/gcp/main.tf:131
Medium Apply security context to your containers
Apply security context to your containers
Where
- ../../suite-core/config/deployment-packs/kubernetes/manifests/redis-deployment.yaml:1
- ../../suite-core/config/deployment-packs/kubernetes/manifests/backend-deployment.yaml:1
- ../../suite-core/config/deployment-packs/kubernetes/manifests/mongodb-deployment.yaml:1
- ../../suite-core/config/kubernetes/enterprise/frontend-deployment.yaml:1
- ../../suite-core/config/kubernetes/enterprise/backend-deployment.yaml:1
Medium Apply security context to your pods and containers
Apply security context to your pods and containers
Where
- ../../suite-core/config/deployment-packs/aws/terraform/main.tf:393
- ../../suite-core/config/deployment-packs/azure/terraform/main.tf:222
- ../../suite-core/config/deployment-packs/gcp/terraform/main.tf:302
- ../../suite-core/config/terraform/enterprise/modules/backend/main.tf:42
- ../../suite-core/telemetry_bridge/edge_collector/gcp/main.tf:131
Medium Missing Cost and Usage Report
No AWS Cost and Usage Report (CUR) configured. CUR provides detailed cost tracking and analysis.
How to fix
Enable AWS Cost and Usage Reports to track spending patterns and identify optimization opportunities.
Where
Medium The default namespace should not be used
Medium Ensure that arrays have a maximum number of items
Ensure that arrays have a maximum number of items
Where
Medium Ensure that the global security field has rules defined
Ensure that the global security field has rules defined
Where
Medium Ensure that security operations is not empty.
Ensure that security operations is not empty.
Where
Medium AWS Access Key
AWS Access Key
Where
- ../../suite-integrations/postman/enterprise/ALdeci-2-Discover.postman_collection.json:1227
- ../../suite-integrations/postman/enterprise/ALdeci-2-Discover.postman_collection.json:1227
- ../../suite-integrations/postman/enterprise/ALdeci-7-Scanners-OSS-AutoFix.postman_collection.json:337
- ../../suite-integrations/postman/enterprise/ALdeci-7-Scanners-OSS-AutoFix.postman_collection.json:337
Medium 3 known vulnerabilities in busybox@1.36.1-r29 (dependencytrack/frontend:4.12.3)
How to fix
No fixed version of busybox is available yet. Check whether dependencytrack/frontend:4.12.3 needs busybox at all (a slimmer or distroless base image often drops it), watch the advisory for a fix, or accept the risk with a review date if it isn't reachable in your setup.
Vulnerabilities
- Medium CVE-2025-60876 fixed in no fix yet
- Low CVE-2024-58251 fixed in 1.36.1-r31
- Low CVE-2025-46394 fixed in 1.36.1-r31
Medium Ensure that S3 bucket has a Public Access block
Ensure that S3 bucket has a Public Access block
Where
Medium Ensure that an S3 bucket has a lifecycle configuration
Ensure that an S3 bucket has a lifecycle configuration
Where
Medium Ensure that S3 bucket has cross-region replication enabled
Ensure that S3 bucket has cross-region replication enabled
Where
Medium Ensure CloudWatch log groups retains logs for at least 1 year
Ensure CloudWatch log groups retains logs for at least 1 year
Where
Medium Ensure AWS Load Balancer doesn't use HTTP protocol
Ensure AWS Load Balancer doesn't use HTTP protocol
Where
Medium Ensure that Storage Accounts use replication
Medium Ensure default network access rule for Storage Accounts is set to deny
Ensure default network access rule for Storage Accounts is set to deny
Where
Medium Ensure Storage Accounts adhere to the naming rules
Ensure Storage Accounts adhere to the naming rules
Where
Medium Ensure the base image uses a non latest version tag
Ensure the base image uses a non latest version tag
Where
and 92 more groups with 130 findings
Low 2
Low Unassociated Elastic IP
Elastic IPs are charged if not attached to a running instance or if you have more than one per instance.
How to fix
Release unattached Elastic IPs.
Where
- docker/terraform/vpc.tf:71 $3.65 / mo
Low SQS Max Message Retention
SQS queue configured with the maximum 14-day (1209600 s) message retention. On high-volume queues this inflates storage costs and may indicate unprocessed message buildup.
How to fix
Set retention to the minimum business requirement (e.g., 1–4 days for most queues) and alert on queue depth to catch processing failures early.
Where
Grades use InfraScan Cloud's current formula, so they can differ from the ones first shown for this scan. Findings reflect the repository on 25 Jun 2026; it may have changed since.
Scan your own repository
InfraScan Cloud scans your repositories and AWS accounts, keeps the history and shows how to fix each finding.