Repository scan
opg-incident-response
ministryofjustice/opg-incident-response · branch main · scanned 25 Jun 2026 · 44 resources
High 107
High 79 known vulnerabilities in unknown@unknown (postgres:14)
How to fix
No fixed version of unknown is available yet. Check whether postgres:14 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-48962 fixed in no fix yet
- High CVE-2025-58187 fixed in no fix yet
- High CVE-2025-58188 fixed in no fix yet
- High CVE-2025-61723 fixed in no fix yet
- High CVE-2025-61725 fixed in no fix yet
- High CVE-2025-61726 fixed in no fix yet
- High CVE-2025-61729 fixed in no fix yet
- High CVE-2026-32280 fixed in no fix yet
- High CVE-2026-32281 fixed in no fix yet
- High CVE-2026-32283 fixed in no fix yet
- High CVE-2026-33814 fixed in no fix yet
- High CVE-2026-39820 fixed in no fix yet
- High CVE-2026-48959 fixed in no fix yet
- High CVE-2026-12087 fixed in no fix yet
- High CVE-2025-68121 fixed in no fix yet
- Medium CVE-2025-45582 fixed in no fix yet
- Medium CVE-2025-58183 fixed in no fix yet
- Medium CVE-2025-47912 fixed in no fix yet
- Medium CVE-2025-58186 fixed in no fix yet
- Medium CVE-2025-58189 fixed in no fix yet
- and 59 more
High 15 known vulnerabilities in openssl@3.5.6-r0 (node:lts-alpine3.23@sha256:2bdb65ed1dab192432bc31c95f94155ca5ad7fc1392fb7eb7526ab682fa5bf14)
How to fix
Update openssl from 3.5.6-r0 to 3.5.7-r0 or later in node:lts-alpine3.23@sha256:2bdb65ed1dab192432bc31c95f94155ca5ad7fc1392fb7eb7526ab682fa5bf14. 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 7 known vulnerabilities in unknown@unknown (node:lts-alpine3.23@sha256:2bdb65ed1dab192432bc31c95f94155ca5ad7fc1392fb7eb7526ab682fa5bf14)
How to fix
No fixed version of unknown is available yet. Check whether node:lts-alpine3.23@sha256:2bdb65ed1dab192432bc31c95f94155ca5ad7fc1392fb7eb7526ab682fa5bf14 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-12151 fixed in no fix yet
- Medium CVE-2026-42338 fixed in no fix yet
- Medium CVE-2026-9679 fixed in no fix yet
- Medium CVE-2026-45149 fixed in no fix yet
- Medium CVE-2026-53655 fixed in no fix yet
- Low CVE-2026-11525 fixed in no fix yet
- Low CVE-2026-6733 fixed in no fix yet
High 6 known vulnerabilities in stdlib@1.24.6 (postgres:14)
How to fix
Update stdlib from 1.24.6 to 1.25.8 or later in postgres:14. 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.25.8); 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-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 53
Medium Ensure Secrets Manager secrets should have automatic rotation enabled
Ensure Secrets Manager secrets should have automatic rotation 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 every security group and rule has a description
Ensure every security group and rule has a description
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 1 known vulnerability in busybox@1.37.0-r30 (node:lts-alpine3.23@sha256:2bdb65ed1dab192432bc31c95f94155ca5ad7fc1392fb7eb7526ab682fa5bf14)
How to fix
No fixed version of busybox is available yet. Check whether node:lts-alpine3.23@sha256:2bdb65ed1dab192432bc31c95f94155ca5ad7fc1392fb7eb7526ab682fa5bf14 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 Ensure Postgres RDS as aws_rds_cluster has Query Logging enabled
Ensure Postgres RDS as aws_rds_cluster has Query Logging enabled
Where
Medium Ensure S3 buckets should have event notifications enabled
Ensure S3 buckets should have event notifications enabled
Where
Medium Ensure AWS ALB attached WAFv2 WebACL is configured with AMR for Log4j Vulnerability
Ensure AWS ALB attached WAFv2 WebACL is configured with AMR for Log4j Vulnerability
How to fix
See Checkov documentation for remediation guidance.
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 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 S3 bucket has cross-region replication enabled
Ensure that S3 bucket has cross-region replication enabled
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
Medium Ensure RDS cluster has IAM authentication enabled
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 DB instance gets all minor upgrades automatically
Ensure DB instance gets all minor upgrades automatically
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 S3 lifecycle configuration sets period for aborting failed uploads
Ensure S3 lifecycle configuration sets period for aborting failed uploads
Where
Medium Ensure RDS cluster configured to copy tags to snapshots
Ensure RDS cluster configured to copy tags to snapshots
Where
Medium Ensure ECS Fargate services run on the latest Fargate platform version
Ensure ECS Fargate services run on the latest Fargate platform version
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 container insights are enabled on ECS cluster
Medium Ensure that CloudWatch Log Group specifies retention days
Ensure that CloudWatch Log Group specifies retention days
Where
Medium Ensure the ELBv2 (Application/Network) has access logging enabled
Ensure the ELBv2 (Application/Network) has access logging enabled
Where
Medium CloudWatch Logs Without Retention
CloudWatch log group without retention_in_days. Logs are kept indefinitely by default, silently growing to hundreds $/month.
How to fix
Set appropriate retention periods for log groups (e.g., 7, 14, or 30 days).
Where
- terraform/ecs.tf:61 $0.66 / 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
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.