Repository scan
terraform-overdose
suminhong/terraform-overdose · branch main · scanned 25 Jun 2026 · 115 resources
High 417
High 260 known vulnerabilities in unknown@unknown (postgres:16.2)
How to fix
No fixed version of unknown is available yet. Check whether postgres:16.2 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-2024-33601 fixed in no fix yet
- High CVE-2026-48962 fixed in no fix yet
- High CVE-2024-33602 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
- and 240 more
High 131 known vulnerabilities in unknown@unknown (keycloak/keycloak:26.0)
How to fix
No fixed version of unknown is available yet. Check whether keycloak/keycloak:26.0 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-7571 fixed in no fix yet
- High CVE-2026-3872 fixed in no fix yet
- High CVE-2026-42584 fixed in no fix yet
- High CVE-2024-12397 fixed in no fix yet
- High CVE-2026-4282 fixed in no fix yet
- High CVE-2025-24970 fixed in no fix yet
- High CVE-2026-33870 fixed in no fix yet
- High CVE-2026-42198 fixed in no fix yet
- High CVE-2026-42579 fixed in no fix yet
- High CVE-2026-42583 fixed in no fix yet
- High CVE-2026-42587 fixed in no fix yet
- High CVE-2026-42587 fixed in no fix yet
- High CVE-2026-44893 fixed in no fix yet
- High CVE-2026-45416 fixed in no fix yet
- High CVE-2026-4634 fixed in no fix yet
- High CVE-2026-50010 fixed in no fix yet
- High CVE-2026-7307 fixed in no fix yet
- High CVE-2026-7507 fixed in no fix yet
- High CVE-2025-6965 fixed in no fix yet
- High CVE-2026-2092 fixed in no fix yet
- and 111 more
High 14 known vulnerabilities in stdlib@1.18.2 (postgres:16.2)
How to fix
Update stdlib from 1.18.2 to 1.18.4 or later in postgres:16.2. 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 8 known vulnerabilities in LC_ADDRESS@unknown (keycloak/keycloak:26.0)
How to fix
No fixed version of LC_ADDRESS is available yet. Check whether keycloak/keycloak:26.0 needs LC_ADDRESS 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-4046 fixed in no fix yet
- High CVE-2026-0861 fixed in no fix yet
- Medium CVE-2025-8058 fixed in no fix yet
- Medium CVE-2026-0915 fixed in no fix yet
- Medium CVE-2025-0395 fixed in no fix yet
- Medium CVE-2025-5702 fixed in no fix yet
- Medium CVE-2025-4802 fixed in no fix yet
- Low CVE-2025-15281 fixed in no fix yet
High 1 known vulnerability in krb5@1.20.1-2%2Bdeb12u1 (postgres:16.2)
How to fix
Update krb5 from 1.20.1-2%2Bdeb12u1 to 1.20.1-2+deb12u2 or later in postgres:16.2. 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.20.1-2+deb12u2); 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-37371 fixed in 1.20.1-2+deb12u2
High 1 known vulnerability in less@590-2 (postgres:16.2)
How to fix
Update less from 590-2 to 590-2.1~deb12u2 or later in postgres:16.2. 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 590-2.1~deb12u2); 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-48624 fixed in 590-2.1~deb12u2
High Unencrypted EBS Volume
EBS volume is not encrypted. This is a security risk and often indicates unmanaged infrastructure.
How to fix
Enable encryption for EBS volumes.
Where
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
Medium 281
Medium Ensure an IAM role is attached to EC2 instance
Ensure an IAM role is attached to EC2 instance
Where
- ../../appendix/C-5.tf:5
- ../../part2/4-1.tf:1
- ../../part2/4-10.tf:6
- ../../part2/4-11.tf:6
- ../../part2/4-12.tf:6
- ../../part2/4-19.tf:8
- ../../part2/4-2.tf:1
- ../../part2/4-20.tf:1
- ../../part2/4-20.tf:6
- ../../part2/4-3.tf:5
- ../../part2/4-4.tf:1
- ../../part2/4-5.tf:11
- ../../part2/4-9.tf:6
- ../../part2/5-10.tf:2
- ../../part3/8-2.tf:10
- ../../part5/chapter15/provider_example/terraform_data.tf:13
- ../../part5/chapter15/provider_example/terraform_data.tf:26
- ../../part2/4-1.tf:1
- ../../part2/4-1.tf:1
- ../../part2/4-2.tf:1
- and 4 more
Medium Ensure that detailed monitoring is enabled for EC2 instances
Ensure that detailed monitoring is enabled for EC2 instances
Where
- ../../appendix/C-5.tf:5
- ../../modules/chapter13_ec2/main.tf:48
- ../../part2/4-1.tf:1
- ../../part2/4-1.tf:1
- ../../part2/4-1.tf:1
- ../../part2/4-10.tf:6
- ../../part2/4-11.tf:6
- ../../part2/4-19.tf:8
- ../../part2/4-2.tf:1
- ../../part2/4-2.tf:1
- ../../part2/4-2.tf:1
- ../../part2/4-20.tf:1
- ../../part2/4-20.tf:6
- ../../part2/4-3.tf:5
- ../../part2/4-3.tf:5
- ../../part2/4-3.tf:5
- ../../part2/4-4.tf:1
- ../../part2/4-4.tf:1
- ../../part2/4-5.tf:11
- ../../part2/4-9.tf:6
- and 4 more
Medium Ensure that EC2 is EBS optimized
Ensure that EC2 is EBS optimized
Where
- ../../appendix/C-5.tf:5
- ../../modules/chapter13_ec2/main.tf:48
- ../../part2/4-1.tf:1
- ../../part2/4-1.tf:1
- ../../part2/4-1.tf:1
- ../../part2/4-10.tf:6
- ../../part2/4-11.tf:6
- ../../part2/4-19.tf:8
- ../../part2/4-2.tf:1
- ../../part2/4-2.tf:1
- ../../part2/4-2.tf:1
- ../../part2/4-20.tf:1
- ../../part2/4-20.tf:6
- ../../part2/4-3.tf:5
- ../../part2/4-3.tf:5
- ../../part2/4-3.tf:5
- ../../part2/4-4.tf:1
- ../../part2/4-4.tf:1
- ../../part2/4-5.tf:11
- ../../part2/4-9.tf:6
- and 4 more
Medium Ensure Instance Metadata Service Version 1 is not enabled
Ensure Instance Metadata Service Version 1 is not enabled
Where
- ../../appendix/C-5.tf:5
- ../../modules/chapter13_ec2/main.tf:48
- ../../part2/4-1.tf:1
- ../../part2/4-1.tf:1
- ../../part2/4-1.tf:1
- ../../part2/4-10.tf:6
- ../../part2/4-11.tf:6
- ../../part2/4-19.tf:8
- ../../part2/4-2.tf:1
- ../../part2/4-2.tf:1
- ../../part2/4-2.tf:1
- ../../part2/4-20.tf:1
- ../../part2/4-20.tf:6
- ../../part2/4-3.tf:5
- ../../part2/4-3.tf:5
- ../../part2/4-3.tf:5
- ../../part2/4-4.tf:1
- ../../part2/4-4.tf:1
- ../../part2/4-5.tf:11
- ../../part2/4-9.tf:6
- and 4 more
Medium Ensure all data stored in the Launch configuration or instance Elastic Blocks Store is securely encrypted
Ensure all data stored in the Launch configuration or instance Elastic Blocks Store is securely encrypted
Where
- ../../appendix/C-5.tf:5
- ../../part2/4-1.tf:1
- ../../part2/4-1.tf:1
- ../../part2/4-1.tf:1
- ../../part2/4-10.tf:6
- ../../part2/4-11.tf:6
- ../../part2/4-19.tf:8
- ../../part2/4-2.tf:1
- ../../part2/4-2.tf:1
- ../../part2/4-2.tf:1
- ../../part2/4-20.tf:1
- ../../part2/4-20.tf:6
- ../../part2/4-3.tf:5
- ../../part2/4-3.tf:5
- ../../part2/4-3.tf:5
- ../../part2/4-4.tf:1
- ../../part2/4-4.tf:1
- ../../part2/4-5.tf:11
- ../../part2/4-9.tf:6
- ../../part2/5-10.tf:2
- and 3 more
Medium Missing Spot Instance Usage
No spot instances detected. Spot instances can save 50-90% on compute costs for interruptible workloads.
How to fix
Use spot instances for batch jobs, data analysis, and optional tasks. Consider aws_spot_instance_request or spot_price in launch templates.
Where
- appendix/C-5.tf:5 $19.68 / mo
- part5/chapter15/provider_example/terraform_data.tf:13 $19.68 / mo
- modules/chapter13_ec2/main.tf:48 $19.68 / mo
- part2/4-19.tf:2 $19.68 / mo
- part2/4-10.tf:6 $19.68 / mo
- part2/4-11.tf:6 $19.68 / mo
- part2/4-20.tf:1 $19.68 / mo
- part2/4-9.tf:6 $19.68 / mo
- part2/4-5.tf:11 $19.68 / mo
- part2/4-3.tf:5 $19.68 / mo
- part2/5-10.tf:2 $19.68 / mo
- part2/4-1.tf:1 $19.68 / mo
- part2/4-4.tf:1 $19.68 / mo
- part2/4-2.tf:1 $19.68 / mo
- part2/4-12.tf:6 $19.68 / mo
- part3/8-2.tf:10 $19.68 / mo
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
- part5/chapter16/provider.tf:1
- part5/chapter17/provider.tf:1
- part5/chapter15/env/provider.tf:1
- part2/4-17.tf:2
- part2/5-5.tf:2
- part2/5-9.tf:7
- part2/5-11.tf:2
- part2/4-18.tf:2
- part2/4-16.tf:1
- part2/5-6.tf:2
- part4/chapter11_13/env/provider.tf:1
- part4/chapter14/env_seoul/provider.tf:1
- part4/chapter14/env_network/provider.tf:1
- part4/chapter14/env_virginia/provider.tf:1
Medium Ensure that Security Groups are attached to another resource
Ensure that Security Groups are attached to another resource
Where
Medium Ensure every security group and rule has a description
Ensure every security group and rule has a description
Where
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 S3 buckets should have event notifications enabled
Ensure S3 buckets should have event notifications enabled
Where
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 all data stored in the S3 bucket have versioning enabled
Ensure all data stored in the S3 bucket have versioning enabled
Where
Medium Ensure VPC flow logging is enabled in all VPCs
Ensure VPC flow logging is enabled in all VPCs
Where
Medium Ensure the default security group of every VPC restricts all traffic
Ensure the default security group of every VPC restricts all traffic
Where
Medium Ensure Terraform module sources use a commit hash
Ensure Terraform module sources use a commit hash
Where
Medium Missing S3 Lifecycle Policy
S3 bucket without lifecycle rules. Objects are retained indefinitely, increasing storage costs.
How to fix
Define lifecycle rules to transition objects to cheaper storage classes (e.g., Glacier) or delete them after a retention period.
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 that enhanced monitoring is enabled for Amazon RDS instances
Ensure that enhanced monitoring is enabled for Amazon RDS instances
Where
Medium Ensure that respective logs of Amazon Relational Database Service (Amazon RDS) are enabled
Ensure that respective logs of Amazon Relational Database Service (Amazon RDS) are enabled
Where
Medium Ensure that RDS instances have Multi-AZ enabled
Ensure that RDS instances have Multi-AZ enabled
Where
Medium Ensure all data stored in the RDS is securely encrypted at rest
Ensure all data stored in the RDS is securely encrypted at rest
Where
Medium Ensure RDS database has IAM authentication enabled
Ensure RDS database has IAM authentication enabled
Where
Medium Ensure DB instance gets all minor upgrades automatically
Ensure DB instance gets all minor upgrades automatically
Where
Medium Ensure that AWS database instances have deletion protection enabled
Ensure that AWS database instances have deletion protection enabled
Where
Medium Ensure Terraform module sources use a tag with a version number
Ensure Terraform module sources use a tag with a version number
Where
Medium Ensure that all EIP addresses allocated to a VPC are attached to EC2 instances
Ensure that all EIP addresses allocated to a VPC are attached to EC2 instances
Where
Medium Ensure that only encrypted EBS volumes are attached to EC2 instances
Ensure that only encrypted EBS volumes are attached to EC2 instances
Where
Medium Ensure Postgres RDS as aws_db_instance has Query Logging enabled
Ensure Postgres RDS as aws_db_instance has Query Logging enabled
Where
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 that RDS clusters has backup plan of AWS Backup
Ensure that RDS clusters has backup plan of AWS Backup
Where
Medium Ensure that load balancer is using at least TLS 1.2
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 RDS clusters have deletion protection enabled
Ensure that RDS clusters have deletion protection enabled
Where
and 34 more groups with 34 findings
Low 17
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
- part5/chapter16/provider.tf:1
- part5/chapter17/provider.tf:1
- part5/chapter15/env/provider.tf:1
- part2/4-17.tf:2
- part2/5-5.tf:2
- part2/5-9.tf:7
- part2/5-11.tf:2
- part2/4-18.tf:2
- part2/4-16.tf:1
- part2/5-6.tf:2
- part4/chapter11_13/env/provider.tf:1
- part4/chapter14/env_seoul/provider.tf:1
- part4/chapter14/env_network/provider.tf:1
- part4/chapter14/env_virginia/provider.tf:1
Low 1 known vulnerability in gcc-12@12.2.0-14 (postgres:16.2)
How to fix
No fixed version of gcc-12 is available yet. Check whether postgres:16.2 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%2Bdeb12u1 (postgres:16.2)
How to fix
No fixed version of perl is available yet. Check whether postgres:16.2 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 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
- modules/chapter11_vpc/gateway.tf:40 $3.65 / mo
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.