Repository scan
sebt-self-service-portal
codeforamerica/sebt-self-service-portal · branch main · scanned 25 Jun 2026 · 65 resources
High 121
High 72 known vulnerabilities in unknown@unknown (rediscommander/redis-commander:latest)
How to fix
No fixed version of unknown is available yet. Check whether rediscommander/redis-commander:latest 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-2022-46175 fixed in no fix yet
- High CVE-2026-26960 fixed in no fix yet
- High CVE-2021-27290 fixed in no fix yet
- High CVE-2021-3807 fixed in no fix yet
- High CVE-2021-3807 fixed in no fix yet
- High CVE-2021-3807 fixed in no fix yet
- High CVE-2022-24999 fixed in no fix yet
- High CVE-2022-24999 fixed in no fix yet
- High CVE-2022-24999 fixed in no fix yet
- High CVE-2022-25881 fixed in no fix yet
- High CVE-2022-25883 fixed in no fix yet
- High CVE-2022-25883 fixed in no fix yet
- High CVE-2022-3517 fixed in no fix yet
- High CVE-2022-38900 fixed in no fix yet
- High CVE-2025-65945 fixed in no fix yet
- High CVE-2026-27903 fixed in no fix yet
- High CVE-2026-27904 fixed in no fix yet
- High CVE-2026-4867 fixed in no fix yet
- High CVE-2021-4435 fixed in no fix yet
- High CVE-2024-21538 fixed in no fix yet
- and 52 more
High 15 known vulnerabilities in openssl@3.5.6-r0 (jaegertracing/jaeger:latest)
How to fix
Update openssl from 3.5.6-r0 to 3.5.7-r0 or later in jaegertracing/jaeger:latest. 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.5.7-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-2026-34181 fixed in 3.5.7-r0
- High CVE-2026-34180 fixed in 3.5.7-r0
- High CVE-2026-34183 fixed in 3.5.7-r0
- High CVE-2026-42764 fixed in 3.5.7-r0
- High CVE-2026-45445 fixed in 3.5.7-r0
- High CVE-2026-9076 fixed in 3.5.7-r0
- High CVE-2026-7383 fixed in 3.5.7-r0
- High CVE-2026-45447 fixed in 3.5.7-r0
- High CVE-2026-34182 fixed in 3.5.7-r0
- Medium CVE-2026-45446 fixed in 3.5.7-r0
- Medium CVE-2026-42769 fixed in 3.5.7-r0
- Medium CVE-2026-42766 fixed in 3.5.7-r0
- Medium CVE-2026-42767 fixed in 3.5.7-r0
- Low CVE-2026-42768 fixed in 3.5.7-r0
- Low CVE-2026-42770 fixed in 3.5.7-r0
High 14 known vulnerabilities in nodejs@12.22.1-r0 (rediscommander/redis-commander:latest)
How to fix
Update nodejs from 12.22.1-r0 to 12.22.10-r0 or later in rediscommander/redis-commander:latest. 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 12.22.10-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-2021-44531 fixed in 12.22.10-r0
- High CVE-2021-22940 fixed in no fix yet
- High CVE-2021-39134 fixed in 12.22.6-r0
- High CVE-2021-39135 fixed in 12.22.6-r0
- High CVE-2022-21824 fixed in 12.22.10-r0
- High CVE-2021-22930 fixed in 12.22.4-r0
- High CVE-2021-22931 fixed in 12.22.5-r0
- Medium CVE-2021-22918 fixed in 12.22.2-r0
- Medium CVE-2021-22939 fixed in 12.22.5-r0
- Medium CVE-2021-44532 fixed in 12.22.10-r0
- Medium CVE-2021-44533 fixed in 12.22.10-r0
- Medium CVE-2021-3672 fixed in 12.22.5-r0
- Medium CVE-2021-22959 fixed in 12.22.10-r0
- Medium CVE-2021-22960 fixed in 12.22.10-r0
High 11 known vulnerabilities in busybox@1.31.1-r20 (rediscommander/redis-commander:latest)
How to fix
Update busybox from 1.31.1-r20 to 1.31.1-r21 or later in rediscommander/redis-commander:latest. 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.31.1-r21); 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-2021-42378 fixed in 1.31.1-r21
- High CVE-2021-42379 fixed in 1.31.1-r21
- High CVE-2021-42380 fixed in 1.31.1-r21
- High CVE-2021-42381 fixed in 1.31.1-r21
- High CVE-2021-42382 fixed in 1.31.1-r21
- High CVE-2021-42383 fixed in 1.31.1-r21
- High CVE-2021-42384 fixed in 1.31.1-r21
- High CVE-2021-42385 fixed in 1.31.1-r21
- High CVE-2021-42386 fixed in 1.31.1-r21
- High CVE-2022-28391 fixed in 1.31.1-r22
- Medium CVE-2021-42374 fixed in 1.31.1-r21
High 3 known vulnerabilities in openssl@1.1.1k-r0 (rediscommander/redis-commander:latest)
How to fix
Update openssl from 1.1.1k-r0 to 1.1.1l-r0 or later in rediscommander/redis-commander:latest. 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.1l-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-2021-3712 fixed in 1.1.1l-r0
- High CVE-2022-0778 fixed in 1.1.1n-r0
- High CVE-2021-3711 fixed in 1.1.1l-r0
High 2 known vulnerabilities in zlib@1.2.11-r3 (rediscommander/redis-commander:latest)
How to fix
Update zlib from 1.2.11-r3 to 1.2.12-r0 or later in rediscommander/redis-commander:latest. 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.12-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-2018-25032 fixed in 1.2.12-r0
- High CVE-2022-37434 fixed in 1.2.12-r2
High 1 known vulnerability in unknown@unknown (axllent/mailpit)
How to fix
No fixed version of unknown is available yet. Check whether axllent/mailpit 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-2023-42821 fixed in no fix yet
High 1 known vulnerability in stdlib@1.26.3 (jaegertracing/jaeger:latest)
How to fix
Update stdlib from 1.26.3 to 1.26.4 or later in jaegertracing/jaeger:latest. 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.26.4); 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-2026-42504 fixed in 1.26.4
High 1 known vulnerability in apk-tools@2.10.6-r0 (rediscommander/redis-commander:latest)
How to fix
Update apk-tools from 2.10.6-r0 to 2.10.7-r0 or later in rediscommander/redis-commander:latest. 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.10.7-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-2021-36159 fixed in 2.10.7-r0
High 1 known vulnerability in gcc@9.3.0-r2 (rediscommander/redis-commander:latest)
How to fix
No fixed version of gcc is available yet. Check whether rediscommander/redis-commander:latest needs gcc 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-2021-37322 fixed in no fix yet
Medium 86
Medium Ensure Terraform module sources use a commit hash
Ensure Terraform module sources use a commit hash
Where
- ../../tofu/config/dev-co/bootstrap/main.tf:1
- ../../tofu/config/dev-co/main.tf:11
- ../../tofu/config/dev-co/main.tf:32
- ../../tofu/config/dev-co/main.tf:61
- ../../tofu/config/dev-co/main.tf:164
- ../../tofu/config/dev-dc/bootstrap/main.tf:1
- ../../tofu/config/dev-dc/main.tf:11
- ../../tofu/config/dev-dc/main.tf:32
- ../../tofu/config/dev-dc/main.tf:61
- ../../tofu/config/dev-dc/main.tf:131
- ../../tofu/modules/sebt_application/main.tf:13
- ../../tofu/modules/sebt_application/main.tf:99
- ../../tofu/modules/sebt_application/main.tf:148
- ../../tofu/modules/sebt_application/main.tf:201
Medium Ensure that ECR repositories are encrypted using KMS
Ensure that ECR repositories are encrypted using KMS
Where
Medium Ensure ECR Image Tags are immutable
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 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 Ensure access is controlled through SSO and not AWS IAM defined users
Ensure access is controlled through SSO and not AWS IAM defined users
Where
Medium Ensure IAM policies does not allow write access without constraints
Ensure IAM policies does not allow write access without constraints
Where
Medium Ensure no IAM policies documents allow "*" as a statement's resource for restrictable actions
Ensure no IAM policies documents allow "*" as a statement's resource for restrictable actions
Where
Medium Ensure IAM policies are attached only to groups or roles (Reducing access management complexity may in-turn reduce opportunity for a principal to inadvertently receive or retain excessive privileges.)
Ensure IAM policies are attached only to groups or roles (Reducing access management complexity may in-turn reduce opportunity for a principal to inadvertently receive or retain excessive privileges.)
Where
Medium 2 known vulnerabilities in unknown@unknown (jaegertracing/jaeger:latest)
How to fix
No fixed version of unknown is available yet. Check whether jaegertracing/jaeger:latest 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
- Medium CVE-2026-42507 fixed in no fix yet
- Medium CVE-2026-27145 fixed in no fix yet
Medium Ensure AWS IAM policy does not allow full IAM privileges
Ensure AWS IAM policy does not allow full IAM privileges
Where
Medium Ensure IAM policies does not allow privilege escalation
Ensure IAM policies does not allow privilege escalation
Where
Medium Ensure IAM policies does not allow credentials exposure
Ensure IAM policies does not allow credentials exposure
Where
Medium Ensure IAM policies does not allow data exfiltration
Ensure IAM policies does not allow data exfiltration
Where
Medium Ensure IAM policies does not allow permissions management / resource exposure without constraints
Ensure IAM policies does not allow permissions management / resource exposure without constraints
Where
Medium 1 known vulnerability in busybox@1.37.0-r30 (jaegertracing/jaeger:latest)
How to fix
No fixed version of busybox is available yet. Check whether jaegertracing/jaeger:latest 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
Medium 1 known vulnerability in busybox@1.37.0-r14 (redis:7-alpine)
How to fix
No fixed version of busybox is available yet. Check whether redis:7-alpine 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
Medium 1 known vulnerability in util-linux@2.40.4-r1 (redis:7-alpine)
How to fix
No fixed version of util-linux is available yet. Check whether redis:7-alpine needs util-linux 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-2026-27456 fixed in no fix yet
Medium 1 known vulnerability in c-ares@1.16.1-r0 (rediscommander/redis-commander:latest)
How to fix
Update c-ares from 1.16.1-r0 to 1.17.2-r0 or later in rediscommander/redis-commander:latest. 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.17.2-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
- Medium CVE-2021-3672 fixed in 1.17.2-r0
Medium 1 known vulnerability in ejs@2.7.4 (rediscommander/redis-commander:latest)
How to fix
Update ejs from 2.7.4 to 3.1.10 or later in rediscommander/redis-commander:latest. 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.1.10); 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
- Medium CVE-2024-33883 fixed in 3.1.10
Medium Ensure CloudFront distribution has a response headers policy attached
Ensure CloudFront distribution has a response headers policy attached
Where
Medium Ensure Domain Name System Security Extensions (DNSSEC) signing is enabled for Amazon Route 53 public hosted zones
Ensure Domain Name System Security Extensions (DNSSEC) signing is enabled for Amazon Route 53 public hosted zones
Where
Medium Ensure Domain Name System (DNS) query logging is enabled for Amazon Route 53 hosted zones
Ensure Domain Name System (DNS) query logging is enabled for Amazon Route 53 hosted zones
Where
Medium Ensure AWS CloudFront attached WAFv2 WebACL is configured with AMR for Log4j Vulnerability
Ensure AWS CloudFront attached WAFv2 WebACL is configured with AMR for Log4j Vulnerability
Where
Medium Ensure RDS instance with copy tags to snapshots is enabled
Ensure RDS instance with copy tags to snapshots is enabled
Where
Medium Ensure S3 buckets should have event notifications enabled
Ensure S3 buckets should have event notifications enabled
Where
Medium Ensure that AWS Lambda function is configured for function-level concurrent execution limit
Ensure that AWS Lambda function is configured for function-level concurrent execution limit
Where
Medium Ensure that AWS Lambda function is configured for a Dead Letter Queue(DLQ)
Ensure that AWS Lambda function is configured for a Dead Letter Queue(DLQ)
Where
Medium Ensure that AWS Lambda function is configured inside a VPC
Ensure that AWS Lambda function is configured inside a VPC
Where
Medium Ensure that enhanced monitoring is enabled for Amazon RDS instances
Ensure that enhanced monitoring is enabled for Amazon RDS instances
Where
Medium Ensure that S3 bucket has cross-region replication enabled
Ensure that S3 bucket has cross-region replication enabled
Where
Medium Ensure that Secrets Manager secret is encrypted using KMS CMK
Ensure that Secrets Manager secret is encrypted using KMS CMK
Where
Medium Ensure that RDS instances have Multi-AZ enabled
Ensure that RDS instances have Multi-AZ enabled
Where
Medium Ensure that CloudWatch Log Group is encrypted by KMS
Ensure that CloudWatch Log Group is encrypted by KMS
Where
Medium Check encryption settings for Lambda environmental variable
Check encryption settings for Lambda environmental variable
Where
Medium Ensure DB instance gets all minor upgrades automatically
Ensure DB instance gets all minor upgrades automatically
Where
Medium Ensure every security group and rule has a description
Ensure every security group and rule has a description
Where
Medium Ensure AWS Lambda function is configured to validate code-signing
Ensure AWS Lambda function is configured to validate code-signing
Where
Medium Ensure that AWS database instances have deletion protection enabled
Ensure that AWS database instances have deletion protection enabled
Where
Medium Ensure CloudFront distributions should have origin failover configured
Ensure CloudFront distributions should have origin failover configured
Where
and 5 more groups with 5 findings
Low 4
Low Missing AWS Budget
No AWS budget configured. Budgets help monitor and control spending with alerts.
How to fix
Create AWS budgets with alerts for forecasted and actual costs to avoid unexpected charges.
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.