Repository scan
brutalismbot
beachplum-io/brutalismbot · branch main · scanned 25 Jun 2026 · 224 resources
High 247
High 242 known vulnerabilities in unknown@unknown (amazon/dynamodb-local)
How to fix
No fixed version of unknown is available yet. Check whether amazon/dynamodb-local 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-11468 fixed in no fix yet
- High CVE-2025-11468 fixed in no fix yet
- High CVE-2025-15282 fixed in no fix yet
- High CVE-2025-15282 fixed in no fix yet
- High CVE-2025-15467 fixed in no fix yet
- High CVE-2025-15467 fixed in no fix yet
- High CVE-2025-15467 fixed in no fix yet
- High CVE-2025-15468 fixed in no fix yet
- High CVE-2025-15468 fixed in no fix yet
- High CVE-2025-15468 fixed in no fix yet
- High CVE-2025-66199 fixed in no fix yet
- High CVE-2025-66199 fixed in no fix yet
- High CVE-2025-66199 fixed in no fix yet
- High CVE-2025-68160 fixed in no fix yet
- High CVE-2025-68160 fixed in no fix yet
- High CVE-2025-68160 fixed in no fix yet
- High CVE-2025-68973 fixed in no fix yet
- High CVE-2025-69418 fixed in no fix yet
- High CVE-2025-69418 fixed in no fix yet
- High CVE-2025-69418 fixed in no fix yet
- and 222 more
High 2 known vulnerabilities in gnupg2-minimal@2.3.7-1.amzn2023.0.5 (amazon/dynamodb-local)
How to fix
Update gnupg2-minimal from 2.3.7-1.amzn2023.0.5 to 2.3.7-1.amzn2023.0.6 or later in amazon/dynamodb-local. 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.3.7-1.amzn2023.0.6); 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-68973 fixed in 2.3.7-1.amzn2023.0.6
- High CVE-2026-24882 fixed in 2.3.7-1.amzn2023.0.7
High 1 known vulnerability in gnupg2@2.3.7-1.amzn2023.0.5 (amazon/dynamodb-local)
How to fix
Update gnupg2 from 2.3.7-1.amzn2023.0.5 to 2.3.7-1.amzn2023.0.7 or later in amazon/dynamodb-local. 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.3.7-1.amzn2023.0.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
- High CVE-2026-24882 fixed in 2.3.7-1.amzn2023.0.7
High 1 known vulnerability in graphite2@1.3.14-7.amzn2023.0.2 (amazon/dynamodb-local)
How to fix
Update graphite2 from 1.3.14-7.amzn2023.0.2 to 1.3.14-7.amzn2023.0.3 or later in amazon/dynamodb-local. 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.3.14-7.amzn2023.0.3); 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-50593 fixed in 1.3.14-7.amzn2023.0.3
High 1 known vulnerability in libtasn1@4.19.0-1.amzn2023.0.5 (amazon/dynamodb-local)
How to fix
Update libtasn1 from 4.19.0-1.amzn2023.0.5 to 4.19.0-1.amzn2023.0.6 or later in amazon/dynamodb-local. 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 4.19.0-1.amzn2023.0.6); 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-13151 fixed in 4.19.0-1.amzn2023.0.6
Medium 197
Medium Ensure State Machine has X-Ray tracing enabled
Ensure State Machine has X-Ray tracing enabled
Where
- ../../blue/bluesky/send-post/main.tf:223
- ../../blue/mail/terraform.tf:262
- ../../blue/reddit/pop-backlog/main.tf:196
- ../../blue/reddit/pop/main.tf:276
- ../../blue/slack-beta/app-home/main.tf:229
- ../../blue/slack-beta/delete-message/main.tf:123
- ../../blue/slack-beta/disable/main.tf:150
- ../../blue/slack-beta/enable/main.tf:150
- ../../blue/slack-beta/reject/main.tf:146
- ../../blue/slack-beta/screen/main.tf:230
- ../../blue/slack-beta/states-errors/main.tf:128
- ../../blue/slack-beta/states-retry/main.tf:140
- ../../blue/slack/create-posts/main.tf:240
- ../../blue/slack/install/main.tf:118
- ../../blue/slack/send-post/main.tf:153
- ../../blue/slack/uninstall/main.tf:161
- ../../blue/twitter/send-post/main.tf:224
- ../../green/backup/main.tf:149
Medium Ensure State Machine has execution history logging enabled
Ensure State Machine has execution history logging enabled
Where
- ../../blue/bluesky/send-post/main.tf:223
- ../../blue/mail/terraform.tf:262
- ../../blue/reddit/pop-backlog/main.tf:196
- ../../blue/reddit/pop/main.tf:276
- ../../blue/slack-beta/app-home/main.tf:229
- ../../blue/slack-beta/delete-message/main.tf:123
- ../../blue/slack-beta/disable/main.tf:150
- ../../blue/slack-beta/enable/main.tf:150
- ../../blue/slack-beta/reject/main.tf:146
- ../../blue/slack-beta/screen/main.tf:230
- ../../blue/slack-beta/states-errors/main.tf:128
- ../../blue/slack-beta/states-retry/main.tf:140
- ../../blue/slack/create-posts/main.tf:240
- ../../blue/slack/install/main.tf:118
- ../../blue/slack/send-post/main.tf:153
- ../../blue/slack/uninstall/main.tf:161
- ../../blue/twitter/send-post/main.tf:224
- ../../green/backup/main.tf:149
Medium Ensure API GatewayV2 routes specify an authorization type
Ensure API GatewayV2 routes specify an authorization type
Where
- ../../blue/slack-beta/api/main.tf:86
- ../../blue/slack-beta/api/main.tf:86
- ../../blue/slack-beta/api/main.tf:86
- ../../blue/slack-beta/api/main.tf:86
- ../../blue/slack-beta/api/main.tf:86
- ../../blue/slack-beta/api/main.tf:86
- ../../blue/slack-beta/api/main.tf:86
- ../../blue/slack-beta/api/main.tf:86
- ../../blue/slack-beta/api/main.tf:86
- ../../blue/slack/api/main.tf:84
- ../../blue/slack/api/main.tf:84
- ../../blue/slack/api/main.tf:84
- ../../blue/slack/api/main.tf:84
- ../../blue/slack/api/main.tf:84
- ../../blue/slack/api/main.tf:84
- ../../blue/slack/api/main.tf:84
Medium Ensure that CloudWatch Log Group is encrypted by KMS
Ensure that CloudWatch Log Group is encrypted by KMS
Where
- ../../blue/bluesky/send-post/main.tf:119
- ../../blue/mail/terraform.tf:33
- ../../blue/reddit/pop/main.tf:41
- ../../blue/shared/http/main.tf:29
- ../../blue/slack-beta/api/main.tf:94
- ../../blue/slack-beta/api/main.tf:111
- ../../blue/slack-beta/app-home/main.tf:106
- ../../blue/slack-beta/screen/main.tf:127
- ../../blue/slack/api/main.tf:92
- ../../blue/slack/api/main.tf:109
- ../../blue/slack/create-posts/main.tf:138
- ../../blue/twitter/send-post/main.tf:118
- ../../green/backup/main.tf:37
Medium Ensure CloudWatch log groups retains logs for at least 1 year
Ensure CloudWatch log groups retains logs for at least 1 year
Where
- ../../blue/bluesky/send-post/main.tf:119
- ../../blue/mail/terraform.tf:33
- ../../blue/reddit/pop/main.tf:41
- ../../blue/shared/http/main.tf:29
- ../../blue/slack-beta/api/main.tf:94
- ../../blue/slack-beta/api/main.tf:111
- ../../blue/slack-beta/app-home/main.tf:106
- ../../blue/slack-beta/screen/main.tf:127
- ../../blue/slack/api/main.tf:92
- ../../blue/slack/api/main.tf:109
- ../../blue/slack/create-posts/main.tf:138
- ../../blue/twitter/send-post/main.tf:118
- ../../green/backup/main.tf:37
Medium Ensure IAM policies does not allow write access without constraints
Ensure IAM policies does not allow write access without constraints
Where
- ../../blue/bluesky/send-post/main.tf:140
- ../../blue/mail/terraform.tf:53
- ../../blue/mail/terraform.tf:247
- ../../blue/reddit/pop/main.tf:62
- ../../blue/shared/http/main.tf:50
- ../../blue/slack-beta/api/main.tf:132
- ../../blue/slack-beta/app-home/main.tf:127
- ../../blue/slack-beta/screen/main.tf:148
- ../../blue/slack/api/main.tf:130
- ../../blue/slack/create-posts/main.tf:159
- ../../blue/twitter/send-post/main.tf:139
- ../../green/backup/main.tf:58
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
- ../../blue/bluesky/send-post/main.tf:140
- ../../blue/mail/terraform.tf:53
- ../../blue/mail/terraform.tf:247
- ../../blue/reddit/pop/main.tf:62
- ../../blue/shared/http/main.tf:50
- ../../blue/slack-beta/api/main.tf:132
- ../../blue/slack-beta/app-home/main.tf:127
- ../../blue/slack-beta/screen/main.tf:148
- ../../blue/slack/api/main.tf:130
- ../../blue/slack/create-posts/main.tf:159
- ../../blue/twitter/send-post/main.tf:139
- ../../green/backup/main.tf:58
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
- ../../blue/bluesky/send-post/main.tf:163
- ../../blue/mail/terraform.tf:88
- ../../blue/reddit/pop/main.tf:85
- ../../blue/shared/http/main.tf:65
- ../../blue/slack-beta/api/main.tf:161
- ../../blue/slack-beta/app-home/main.tf:163
- ../../blue/slack-beta/screen/main.tf:164
- ../../blue/slack/api/main.tf:159
- ../../blue/slack/create-posts/main.tf:174
- ../../blue/twitter/send-post/main.tf:163
- ../../green/backup/main.tf:81
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
- ../../blue/bluesky/send-post/main.tf:163
- ../../blue/mail/terraform.tf:88
- ../../blue/reddit/pop/main.tf:85
- ../../blue/shared/http/main.tf:65
- ../../blue/slack-beta/api/main.tf:161
- ../../blue/slack-beta/app-home/main.tf:163
- ../../blue/slack-beta/screen/main.tf:164
- ../../blue/slack/api/main.tf:159
- ../../blue/slack/create-posts/main.tf:174
- ../../blue/twitter/send-post/main.tf:163
- ../../green/backup/main.tf:81
Medium Ensure that AWS Lambda function is configured inside a VPC
Ensure that AWS Lambda function is configured inside a VPC
Where
- ../../blue/bluesky/send-post/main.tf:163
- ../../blue/mail/terraform.tf:88
- ../../blue/reddit/pop/main.tf:85
- ../../blue/shared/http/main.tf:65
- ../../blue/slack-beta/api/main.tf:161
- ../../blue/slack-beta/app-home/main.tf:163
- ../../blue/slack-beta/screen/main.tf:164
- ../../blue/slack/api/main.tf:159
- ../../blue/slack/create-posts/main.tf:174
- ../../blue/twitter/send-post/main.tf:163
- ../../green/backup/main.tf:81
Medium Ensure AWS Lambda function is configured to validate code-signing
Ensure AWS Lambda function is configured to validate code-signing
Where
- ../../blue/bluesky/send-post/main.tf:163
- ../../blue/mail/terraform.tf:88
- ../../blue/reddit/pop/main.tf:85
- ../../blue/shared/http/main.tf:65
- ../../blue/slack-beta/api/main.tf:161
- ../../blue/slack-beta/app-home/main.tf:163
- ../../blue/slack-beta/screen/main.tf:164
- ../../blue/slack/api/main.tf:159
- ../../blue/slack/create-posts/main.tf:174
- ../../blue/twitter/send-post/main.tf:163
- ../../green/backup/main.tf:81
Medium X-Ray tracing is enabled for Lambda
X-Ray tracing is enabled for Lambda
Where
- ../../blue/bluesky/send-post/main.tf:163
- ../../blue/mail/terraform.tf:88
- ../../blue/reddit/pop/main.tf:85
- ../../blue/shared/http/main.tf:65
- ../../blue/slack-beta/api/main.tf:161
- ../../blue/slack-beta/app-home/main.tf:163
- ../../blue/slack-beta/screen/main.tf:164
- ../../blue/slack/api/main.tf:159
- ../../blue/slack/create-posts/main.tf:174
- ../../blue/twitter/send-post/main.tf:163
- ../../green/backup/main.tf:81
Medium Check encryption settings for Lambda environmental variable
Check encryption settings for Lambda environmental variable
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 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 EventBridge Scheduler Schedule uses Customer Managed Key (CMK)
Ensure EventBridge Scheduler Schedule uses Customer Managed Key (CMK)
Where
Medium 1 known vulnerability in curl@8.15.0-4.amzn2023.0.1 (amazon/dynamodb-local)
How to fix
Update curl from 8.15.0-4.amzn2023.0.1 to 8.17.0-1.amzn2023.0.3 or later in amazon/dynamodb-local. 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.17.0-1.amzn2023.0.3); 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-2026-3805 fixed in 8.17.0-1.amzn2023.0.3
Medium 1 known vulnerability in curl-minimal@8.15.0-4.amzn2023.0.1 (amazon/dynamodb-local)
How to fix
Update curl-minimal from 8.15.0-4.amzn2023.0.1 to 8.17.0-1.amzn2023.0.3 or later in amazon/dynamodb-local. 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.17.0-1.amzn2023.0.3); 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-2026-3805 fixed in 8.17.0-1.amzn2023.0.3
Medium 1 known vulnerability in expat@2.6.3-1.amzn2023.0.3 (amazon/dynamodb-local)
How to fix
Update expat from 2.6.3-1.amzn2023.0.3 to 2.6.3-1.amzn2023.0.4 or later in amazon/dynamodb-local. 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.6.3-1.amzn2023.0.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
- Medium CVE-2026-25210 fixed in 2.6.3-1.amzn2023.0.4
Medium 1 known vulnerability in libcurl-minimal@8.15.0-4.amzn2023.0.1 (amazon/dynamodb-local)
How to fix
Update libcurl-minimal from 8.15.0-4.amzn2023.0.1 to 8.17.0-1.amzn2023.0.3 or later in amazon/dynamodb-local. 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.17.0-1.amzn2023.0.3); 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-2026-3805 fixed in 8.17.0-1.amzn2023.0.3
Medium 1 known vulnerability in libgcrypt@1.10.2-1.amzn2023.0.2 (amazon/dynamodb-local)
How to fix
Update libgcrypt from 1.10.2-1.amzn2023.0.2 to 1.10.2-1.amzn2023.0.3 or later in amazon/dynamodb-local. 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.10.2-1.amzn2023.0.3); 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-2026-41989 fixed in 1.10.2-1.amzn2023.0.3
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 that an S3 bucket has a lifecycle configuration
Ensure that an S3 bucket has a lifecycle configuration
Where
Medium Ensure DynamoDB Tables are encrypted using a KMS Customer Managed CMK
Ensure DynamoDB Tables are encrypted using a KMS Customer Managed CMK
Where
Medium Ensure all data stored in the SNS topic is encrypted
Ensure all data stored in the SNS topic is encrypted
Where
Medium Ensure DynamoDB point in time recovery (backup) is enabled
Ensure DynamoDB point in time recovery (backup) is enabled
Where
Medium Ensure S3 lifecycle configuration sets period for aborting failed uploads
Ensure S3 lifecycle configuration sets period for aborting failed uploads
Where
Medium Ensure CloudFront distributions should have origin failover configured
Ensure CloudFront distributions should have origin failover configured
Where
Medium Ensure AWS CloudFront web distribution has geo restriction enabled
Ensure AWS CloudFront web distribution has geo restriction enabled
Where
Medium CloudFront Distribution should have WAF enabled
Medium Ensure CloudFront distribution has Access Logging enabled
Ensure CloudFront distribution has Access Logging enabled
Where
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
Low Route53 Health Checks
Route53 health checks incur monthly costs. May not be necessary for all resources.
How to fix
Remove health checks for non-critical resources or personal projects.
Where
- global/api/main.tf:72 $0.50 / 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.