Repository scan
ztmf
CMS-Enterprise/ztmf · branch main · scanned 25 Jun 2026 · 111 resources
High 272
High 231 known vulnerabilities in unknown@unknown (postgres:16.8)
How to fix
No fixed version of unknown is available yet. Check whether postgres:16.8 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-2025-5222 fixed in no fix yet
- High CVE-2025-24528 fixed in no fix yet
- High CVE-2026-42010 fixed in no fix yet
- High CVE-2026-42012 fixed in no fix yet
- High CVE-2025-6965 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-2026-48962 fixed in no fix yet
- High CVE-2025-69419 fixed in no fix yet
- High CVE-2026-42011 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
- and 211 more
High 14 known vulnerabilities in stdlib@1.18.2 (postgres:16.8)
How to fix
Update stdlib from 1.18.2 to 1.18.4 or later in postgres:16.8. 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.18.4
- High CVE-2022-32189 fixed in 1.18.5
- High CVE-2024-34158 fixed in 1.22.7
- High CVE-2026-25679 fixed in 1.25.8
- High CVE-2026-33811 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-42504 fixed in 1.25.11
- Medium CVE-2025-58185 fixed in 1.24.8
- Medium CVE-2025-4673 fixed in 1.23.10
High 10 known vulnerabilities in openssl@3.1.4-r5 (postgres:16.2-alpine3.19)
How to fix
Update openssl from 3.1.4-r5 to 3.1.6-r0 or later in postgres:16.2-alpine3.19. 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.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-2024-4741 fixed in 3.1.6-r0
- High CVE-2024-6119 fixed in 3.1.7-r0
- High CVE-2025-9230 fixed in 3.1.8-r1
- High CVE-2025-15467 fixed in no fix yet
- High CVE-2024-5535 fixed in 3.1.6-r0
- Medium CVE-2024-13176 fixed in 3.1.8-r0
- Medium CVE-2024-9143 fixed in 3.1.7-r1
- Medium CVE-2024-4603 fixed in 3.1.5-r0
- Medium CVE-2024-2511 fixed in 3.1.4-r6
- Medium CVE-2025-9232 fixed in 3.1.8-r1
High 9 known vulnerabilities in libxml2@2.11.7-r0 (postgres:16.2-alpine3.19)
How to fix
Update libxml2 from 2.11.7-r0 to 2.11.8-r0 or later in postgres:16.2-alpine3.19. 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.11.8-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-34459 fixed in 2.11.8-r0
- High CVE-2025-6021 fixed in no fix yet
- High CVE-2024-56171 fixed in 2.11.8-r1
- High CVE-2025-24928 fixed in 2.11.8-r1
- High CVE-2024-40896 fixed in no fix yet
- Medium CVE-2025-32414 fixed in 2.11.8-r3
- Medium CVE-2025-9714 fixed in no fix yet
- Low CVE-2025-27113 fixed in 2.11.8-r2
- Low CVE-2025-32415 fixed in 2.11.8-r3
High 3 known vulnerabilities in musl@1.2.4_git20230717-r4 (postgres:16.2-alpine3.19)
How to fix
Update musl from 1.2.4_git20230717-r4 to 1.2.4_git20230717-r5 or later in postgres:16.2-alpine3.19. 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.4_git20230717-r5); 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.4_git20230717-r5
- High CVE-2026-40200 fixed in 1.2.4_git20230717-r6
- Medium CVE-2026-6042 fixed in 1.2.4_git20230717-r6
High 2 known vulnerabilities in libxslt@1.1.39-r0 (postgres:16.2-alpine3.19)
How to fix
Update libxslt from 1.1.39-r0 to 1.1.39-r1 or later in postgres:16.2-alpine3.19. 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-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-2024-55549 fixed in 1.1.39-r1
- High CVE-2025-24855 fixed in 1.1.39-r1
High 2 known vulnerabilities in xz@5.4.5-r0 (postgres:16.2-alpine3.19)
How to fix
Update xz from 5.4.5-r0 to 5.4.5-r1 or later in postgres:16.2-alpine3.19. 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.4.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-31115 fixed in 5.4.5-r1
- Medium CVE-2024-47611 fixed in no fix yet
High 1 known vulnerability in icu@74.1-r0 (postgres:16.2-alpine3.19)
How to fix
Update icu from 74.1-r0 to 74.1-r1 or later in postgres:16.2-alpine3.19. 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 74.1-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-5222 fixed in 74.1-r1
Medium 97
Medium Ensure Secrets Manager secrets should have automatic rotation enabled
Ensure Secrets Manager secrets should have automatic rotation enabled
Where
- ../../infrastructure/lambda-cert-rotation.tf:117
- ../../infrastructure/secrets.tf:7
- ../../infrastructure/secrets.tf:26
- ../../infrastructure/secrets.tf:38
- ../../infrastructure/secrets.tf:53
- ../../infrastructure/secrets.tf:58
- ../../infrastructure/secrets.tf:70
- ../../infrastructure/secrets.tf:83
- ../../infrastructure/secrets.tf:89
- ../../infrastructure/secrets.tf:94
- ../../infrastructure/secrets.tf:101
- ../../infrastructure/secrets.tf:115
- ../../infrastructure/secrets.tf:132
Medium Ensure that Secrets Manager secret is encrypted using KMS CMK
Ensure that Secrets Manager secret is encrypted using KMS CMK
Where
- ../../infrastructure/secrets.tf:7
- ../../infrastructure/secrets.tf:26
- ../../infrastructure/secrets.tf:38
- ../../infrastructure/secrets.tf:53
- ../../infrastructure/secrets.tf:58
- ../../infrastructure/secrets.tf:70
- ../../infrastructure/secrets.tf:83
- ../../infrastructure/secrets.tf:89
- ../../infrastructure/secrets.tf:94
- ../../infrastructure/secrets.tf:132
Medium 7 known vulnerabilities in busybox@1.36.1-r15 (postgres:16.2-alpine3.19)
How to fix
Update busybox from 1.36.1-r15 to 1.36.1-r17 or later in postgres:16.2-alpine3.19. 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.36.1-r17); 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-2023-42363 fixed in 1.36.1-r17
- Medium CVE-2023-42364 fixed in 1.36.1-r19
- Medium CVE-2023-42365 fixed in 1.36.1-r19
- Medium CVE-2023-42366 fixed in 1.36.1-r16
- Medium CVE-2025-60876 fixed in no fix yet
- Low CVE-2024-58251 fixed in 1.36.1-r21
- Low CVE-2025-46394 fixed in 1.36.1-r21
Medium Ensure that S3 bucket has cross-region replication enabled
Ensure that S3 bucket has cross-region replication 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 the S3 bucket has access logging enabled
Ensure the S3 bucket has access logging enabled
Where
Medium Ensure that an S3 bucket has a lifecycle configuration
Ensure that an S3 bucket has a lifecycle configuration
Where
Medium Ensure S3 buckets should have event notifications enabled
Ensure S3 buckets should have event notifications enabled
Where
Medium Ensure that CloudWatch Log Group is encrypted by KMS
Ensure that CloudWatch Log Group is encrypted by KMS
Where
Medium 2 known vulnerabilities in util-linux@2.39.3-r0 (postgres:16.2-alpine3.19)
How to fix
No fixed version of util-linux is available yet. Check whether postgres:16.2-alpine3.19 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
- Low CVE-2024-28085 fixed in no fix yet
Medium Ensure that Security Groups are attached to another resource
Ensure that Security Groups are attached to another resource
Where
Medium Ensure that S3 bucket has a Public Access block
Ensure that S3 bucket has a Public Access block
Where
Medium Ensure that ECR repositories are encrypted using KMS
Ensure that ECR repositories are encrypted using KMS
Where
Medium Ensure ECR image scanning on push is enabled
Ensure ECR image scanning on push is enabled
Where
Medium Ensure all data stored in the S3 bucket have versioning enabled
Ensure all data stored in the S3 bucket have versioning enabled
Where
Medium Ensure every security group and rule has a description
Ensure every security group and rule has a description
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 CloudWatch log groups retains logs for at least 1 year
Ensure CloudWatch log groups retains logs for at least 1 year
Where
Medium 1 known vulnerability in libgcrypt@1.10.3-r0 (postgres:16.2-alpine3.19)
How to fix
No fixed version of libgcrypt is available yet. Check whether postgres:16.2-alpine3.19 needs libgcrypt 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-41989 fixed in no fix yet
Medium 1 known vulnerability in openldap@2.6.6-r1 (postgres:16.2-alpine3.19)
How to fix
No fixed version of openldap is available yet. Check whether postgres:16.2-alpine3.19 needs openldap 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-22185 fixed in no fix yet
Medium Ensure Postgres RDS as aws_rds_cluster has Query Logging enabled
Ensure Postgres RDS as aws_rds_cluster has Query Logging enabled
Where
Medium AWS SSM Parameter should be Encrypted
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 that RDS clusters has backup plan of AWS Backup
Ensure that RDS clusters has backup plan of AWS Backup
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 enhanced monitoring is enabled for Amazon RDS instances
Ensure that enhanced monitoring is enabled for Amazon RDS instances
Where
Medium Ensure that ALB drops HTTP headers
Medium Ensure that RDS clusters have deletion protection enabled
Ensure that RDS clusters have deletion protection enabled
Where
Medium Ensure RDS cluster has IAM authentication enabled
Ensure RDS cluster has IAM authentication enabled
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 HTTP HTTPS Target group defines Healthcheck
Ensure HTTP HTTPS Target group defines Healthcheck
Where
Medium Ensure AWS Lambda function is configured to validate code-signing
Ensure AWS Lambda function is configured to validate code-signing
Where
Medium Disallow IAM roles, users, and groups from using the AWS AdministratorAccess policy
Disallow IAM roles, users, and groups from using the AWS AdministratorAccess policy
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 CloudFront distributions should have origin failover configured
Ensure CloudFront distributions should have origin failover configured
Where
Medium Ensure RDS cluster configured to copy tags to snapshots
Ensure RDS cluster configured to copy tags to snapshots
Where
Medium Ensure that RDS Cluster log capture is enabled
Medium Ensure RDS Clusters are encrypted using KMS CMKs
Medium Ensure that RDS instances have performance insights enabled
Ensure that RDS instances have performance insights enabled
Where
and 6 more groups with 6 findings
Low 6
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
Low 1 known vulnerability in zlib@1.3.1-r0 (postgres:16.2-alpine3.19)
How to fix
No fixed version of zlib is available yet. Check whether postgres:16.2-alpine3.19 needs zlib 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
- Low CVE-2026-27171 fixed in no fix yet
Low 1 known vulnerability in gcc-12@12.2.0-14 (postgres:16.8)
How to fix
No fixed version of gcc-12 is available yet. Check whether postgres:16.8 needs gcc-12 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
- Low CVE-2022-27943 fixed in no fix yet
Low 1 known vulnerability in perl@5.36.0-7%2Bdeb12u2 (postgres:16.8)
How to fix
No fixed version of perl is available yet. Check whether postgres:16.8 needs perl 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
- Low CVE-2011-4116 fixed in no fix yet
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.