Repository scan
keys-server
reown-com/keys-server · branch main · scanned 25 Jun 2026 · 50 resources
High 430
High 191 known vulnerabilities in unknown@unknown (jaegertracing/opentelemetry-all-in-one:latest)
How to fix
No fixed version of unknown is available yet. Check whether jaegertracing/opentelemetry-all-in-one: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-2989 fixed in no fix yet
- High CVE-2022-2990 fixed in no fix yet
- High CVE-2022-2995 fixed in no fix yet
- High CVE-2026-41567 fixed in no fix yet
- High CVE-2026-42306 fixed in no fix yet
- High CVE-2021-33195 fixed in no fix yet
- High CVE-2023-24539 fixed in no fix yet
- High CVE-2023-29400 fixed in no fix yet
- High CVE-2024-25621 fixed in no fix yet
- High CVE-2019-13509 fixed in no fix yet
- High CVE-2020-29652 fixed in no fix yet
- High CVE-2021-27918 fixed in no fix yet
- High CVE-2021-33194 fixed in no fix yet
- High CVE-2021-33196 fixed in no fix yet
- High CVE-2021-33198 fixed in no fix yet
- High CVE-2021-38561 fixed in no fix yet
- High CVE-2021-39293 fixed in no fix yet
- High CVE-2021-41771 fixed in no fix yet
- High CVE-2021-41772 fixed in no fix yet
- High CVE-2021-43565 fixed in no fix yet
- and 171 more
High 175 known vulnerabilities in unknown@unknown (mongo:4)
How to fix
No fixed version of unknown is available yet. Check whether mongo:4 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-24539 fixed in no fix yet
- High CVE-2023-29400 fixed in no fix yet
- High CVE-2022-27664 fixed in no fix yet
- High CVE-2022-2879 fixed in no fix yet
- High CVE-2022-2880 fixed in no fix yet
- High CVE-2022-29804 fixed in no fix yet
- High CVE-2022-30631 fixed in no fix yet
- High CVE-2022-30633 fixed in no fix yet
- High CVE-2022-41715 fixed in no fix yet
- High CVE-2022-41716 fixed in no fix yet
- High CVE-2022-41720 fixed in no fix yet
- High CVE-2022-41722 fixed in no fix yet
- High CVE-2022-41723 fixed in no fix yet
- High CVE-2022-41724 fixed in no fix yet
- High CVE-2022-41725 fixed in no fix yet
- High CVE-2023-24534 fixed in no fix yet
- High CVE-2023-24536 fixed in no fix yet
- High CVE-2023-24537 fixed in no fix yet
- High CVE-2023-39325 fixed in no fix yet
- High CVE-2023-44487 fixed in no fix yet
- and 155 more
High 24 known vulnerabilities in stdlib@1.18.2 (mongo:4)
How to fix
Update stdlib from 1.18.2 to 1.18.4 or later in mongo:4. 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.18.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-2022-28131 fixed in 1.18.4
- High CVE-2022-30630 fixed in 1.18.4
- High CVE-2022-30632 fixed in 1.18.4
- High CVE-2022-30634 fixed in 1.18.3
- High CVE-2022-30635 fixed in 1.22.7
- High CVE-2022-30635 fixed in 1.18.4
- High CVE-2022-32189 fixed in 1.18.5
- High CVE-2024-34158 fixed in 1.22.7
- High CVE-2024-34158 fixed in 1.22.7
- High CVE-2026-25679 fixed in 1.25.8
- High CVE-2026-25679 fixed in 1.25.8
- High CVE-2026-33811 fixed in 1.25.10
- High CVE-2026-33811 fixed in 1.25.10
- High CVE-2026-39836 fixed in 1.25.10
- High CVE-2026-39836 fixed in 1.25.10
- High CVE-2026-42499 fixed in 1.25.10
- High CVE-2026-42499 fixed in 1.25.10
- High CVE-2026-42504 fixed in 1.25.11
- High CVE-2026-42504 fixed in 1.25.11
- Medium CVE-2024-34155 fixed in 1.22.7
- and 4 more
High 17 known vulnerabilities in stdlib@1.16 (jaegertracing/opentelemetry-all-in-one:latest)
How to fix
Update stdlib from 1.16 to 1.16.12 or later in jaegertracing/opentelemetry-all-in-one: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.16.12); 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-44716 fixed in 1.16.12
- High CVE-2022-23772 fixed in 1.16.14
- High CVE-2022-24675 fixed in 1.17.9
- High CVE-2022-28131 fixed in 1.17.12
- High CVE-2022-30630 fixed in 1.17.12
- High CVE-2022-30632 fixed in 1.17.12
- High CVE-2022-30634 fixed in 1.17.11
- High CVE-2022-30635 fixed in 1.17.12
- High CVE-2022-32189 fixed in 1.17.13
- High CVE-2024-34158 fixed in 1.22.7
- High CVE-2026-25679 fixed in 1.25.8
- High CVE-2026-39836 fixed in 1.25.10
- High CVE-2026-42499 fixed in 1.25.10
- High CVE-2026-42504 fixed in 1.25.11
- Medium CVE-2022-29526 fixed in 1.17.10
- Medium CVE-2025-58185 fixed in 1.24.8
- Medium CVE-2021-36221 fixed in 1.16.7
High 13 known vulnerabilities in net@0.0.0-20210119194325-5f4716e94777 (jaegertracing/opentelemetry-all-in-one:latest)
How to fix
Update net from 0.0.0-20210119194325-5f4716e94777 to 0.0.0-20211209124913-491a49abca63 or later in jaegertracing/opentelemetry-all-in-one: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 0.0.0-20211209124913-491a49abca63); 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-44716 fixed in 0.0.0-20211209124913-491a49abca63
- High CVE-2022-27664 fixed in 0.0.0-20220906165146-f3363e06e74c
- High CVE-2022-41723 fixed in 0.7.0
- High CVE-2026-33814 fixed in 0.53.0
- Medium CVE-2022-41717 fixed in 0.4.0
- Medium CVE-2024-45338 fixed in 0.33.0
- Medium CVE-2025-47911 fixed in 0.45.0
- Medium CVE-2025-58190 fixed in 0.45.0
- Medium CVE-2026-25681 fixed in 0.55.0
- Medium CVE-2026-27136 fixed in 0.55.0
- Medium CVE-2026-42502 fixed in 0.55.0
- Medium CVE-2026-42506 fixed in 0.55.0
- Medium CVE-2026-25680 fixed in 0.55.0
High 6 known vulnerabilities in crypto@0.0.0-20201002170205-7f63de1d35b0 (jaegertracing/opentelemetry-all-in-one:latest)
How to fix
Update crypto from 0.0.0-20201002170205-7f63de1d35b0 to 0.35.0 or later in jaegertracing/opentelemetry-all-in-one: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 0.35.0); 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-22869 fixed in 0.35.0
- High CVE-2025-47913 fixed in 0.43.0
- High CVE-2026-46597 fixed in 0.52.0
- High CVE-2026-42508 fixed in 0.52.0
- High CVE-2026-46595 fixed in 0.52.0
- Medium CVE-2026-46598 fixed in 0.52.0
High 4 known vulnerabilities in crypto@0.14.0 (mongo:4)
How to fix
Update crypto from 0.14.0 to 0.43.0 or later in mongo:4. 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 0.43.0); 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-47913 fixed in 0.43.0
- High CVE-2026-46597 fixed in 0.52.0
- High CVE-2026-42508 fixed in 0.52.0
- Medium CVE-2026-46598 fixed in 0.52.0
Medium 43
Medium Ensure Terraform module sources use a commit hash
Ensure Terraform module sources use a commit hash
Where
- ../../terraform/cloudwatch/context.tf:1
- ../../terraform/cloudwatch/main.tf:1
- ../../terraform/context.tf:1
- ../../terraform/docdb/context.tf:1
- ../../terraform/ecs/cluster.tf:15
- ../../terraform/ecs/context.tf:1
- ../../terraform/monitoring/context.tf:1
- ../../terraform/monitoring/data_sources.tf:1
- ../../terraform/res_dns.tf:6
- ../../terraform/res_network.tf:22
- ../../terraform/res_network.tf:58
- ../../terraform/res_network.tf:103
Medium 3 known vulnerabilities in krb5@1.17-6ubuntu4.4 (mongo:4)
How to fix
Update krb5 from 1.17-6ubuntu4.4 to 1.17-6ubuntu4.9 or later in mongo:4. 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-6ubuntu4.9); 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-2025-24528 fixed in 1.17-6ubuntu4.9
- Low CVE-2024-26458 fixed in 1.17-6ubuntu4.9
- Low CVE-2024-26461 fixed in 1.17-6ubuntu4.9
Medium 2 known vulnerabilities in docker@17.12.0-ce-rc1.0.20200706150819-a40b877fbb9e%2Bincompatible (jaegertracing/opentelemetry-all-in-one:latest)
How to fix
Update docker from 17.12.0-ce-rc1.0.20200706150819-a40b877fbb9e%2Bincompatible to 20.10.18 or later in jaegertracing/opentelemetry-all-in-one: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 20.10.18); 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-2022-36109 fixed in 20.10.18
- Low CVE-2021-41190 fixed in 20.10.11+incompatible
Medium 2 known vulnerabilities in sys@0.0.0-20210119212857-b64e53b001e4 (jaegertracing/opentelemetry-all-in-one:latest)
How to fix
Update sys from 0.0.0-20210119212857-b64e53b001e4 to 0.0.0-20220412211240-33da011f77ad or later in jaegertracing/opentelemetry-all-in-one: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 0.0.0-20220412211240-33da011f77ad); 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-2022-29526 fixed in 0.0.0-20220412211240-33da011f77ad
- Low CVE-2026-39824 fixed in 0.44.0
Medium Ensure all data stored in the SNS topic is encrypted
Ensure all data stored in the SNS topic is encrypted
Where
Medium 1 known vulnerability in glibc@2.31-0ubuntu9.15 (mongo:4)
How to fix
Update glibc from 2.31-0ubuntu9.15 to 2.31-0ubuntu9.17 or later in mongo:4. 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.31-0ubuntu9.17); 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-2025-0395 fixed in 2.31-0ubuntu9.17
Medium 1 known vulnerability in sqlite3@3.31.1-4ubuntu0.6 (mongo:4)
How to fix
Update sqlite3 from 3.31.1-4ubuntu0.6 to 3.31.1-4ubuntu0.7 or later in mongo:4. 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.31.1-4ubuntu0.7); 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-2025-52099 fixed in 3.31.1-4ubuntu0.7
Medium Ensure public facing ALB are protected by WAF
Medium Ensure Secrets Manager secrets should have automatic rotation enabled
Ensure Secrets Manager secrets should have automatic rotation enabled
Where
Medium Ensure KMS key Policy is defined
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 write access without constraints
Ensure IAM policies does not allow write access without constraints
Where
Medium Ensure that ALB drops HTTP headers
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 Load Balancer has deletion protection enabled
Ensure that Load Balancer has deletion protection enabled
Where
Medium Ensure that CloudWatch Log Group is encrypted by KMS
Ensure that CloudWatch Log Group is encrypted by KMS
Where
Medium Ensure ECS Cluster logging is enabled and client to container communication uses CMK
Ensure ECS Cluster logging is enabled and client to container communication uses CMK
Where
Medium Ensure that the Execution Role ARN and the Task Role ARN are different in ECS Task definitions
Ensure that the Execution Role ARN and the Task Role ARN are different in ECS Task definitions
Where
Medium Ensure no security groups allow ingress from 0.0.0.0:0 to port 80
Ensure no security groups allow ingress from 0.0.0.0:0 to port 80
Where
Medium Ensure ECS containers are limited to read-only access to root filesystems
Ensure ECS containers are limited to read-only access to root filesystems
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 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 DocumentDB has an adequate backup retention period
Ensure DocumentDB has an adequate backup retention period
Where
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 the ELBv2 (Application/Network) has access logging enabled
Ensure the ELBv2 (Application/Network) has access logging enabled
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 Load Balancer for Single Instance
Load balancer detected. Verify it's needed - load balancers cost $15-20/month even if unused.
How to fix
Consider if load balancer is necessary for single-instance deployments or low-traffic applications.
Where
Low 1
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.