InfraScan Cloud

Repository scan

nr-bcws-wfnews

bcgov/nr-bcws-wfnews · branch main · scanned 25 Jun 2026 · 148 resources

DOverall
FSecurity
–Reliability · N/A
BCost
460findings · 0 critical, 102 high
—no cost findings with a savings estimate

High 254

High 239 known vulnerabilities in unknown@unknown (postgres:12) Security · 239 CVEs

How to fix

No fixed version of unknown is available yet. Check whether postgres:12 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 219 more
High 14 known vulnerabilities in stdlib@1.18.2 (postgres:12) Security · 14 CVEs

How to fix

Update stdlib from 1.18.2 to 1.18.4 or later in postgres:12. 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 Old Generation Instance Cost · 1 place

Usage of old generation EC2 instances (e.g., t2, m3, c4, r3). Newer generations are often cheaper and faster.

How to fix

Upgrade to current generation instances (e.g., t3, m5, c5, r5).

Where

Medium 204

Medium Ensure top-level permissions are not set to write-all Security · 25 places
Medium Ensure that HEALTHCHECK instructions have been added to container images Security · 12 places
Medium Ensure AWS CloudFront attached WAFv2 WebACL is configured with AMR for Log4j Vulnerability Security · 10 places
Medium The build output cannot be affected by user parameters other than the build entry point and the top-level source location. GitHub Actions workflow_dispatch inputs MUST be empty. Security · 10 places
Medium Verify CloudFront Distribution Viewer Certificate is using TLS v1.2 or higher Security · 8 places
Medium Ensure CloudFront distribution has a default root object configured Security · 8 places
Medium Ensure CloudFront distributions should have origin failover configured Security · 8 places
Medium Ensure ECS services do not have public IP addresses assigned to them automatically Security · 8 places
Medium Ensure AWS Load Balancer doesn't use HTTP protocol Security · 8 places
Medium CloudFront Distribution should have WAF enabled Security · 8 places
Medium Ensure CloudFront distribution has Access Logging enabled Security · 8 places
Medium Ensure that AWS Lambda function is configured for function-level concurrent execution limit Security · 6 places
Medium Ensure that AWS Lambda function is configured for a Dead Letter Queue(DLQ) Security · 6 places
Medium Check encryption settings for Lambda environmental variable Security · 5 places
Medium Ensure AWS Lambda function is configured to validate code-signing Security · 5 places
Medium X-Ray tracing is enabled for Lambda Security · 5 places
Medium Ensure that a user for the container has been created Security · 5 places
Medium Ensure CloudFront response header policy enforces Strict Transport Security Security · 4 places
Medium Ensure Lambda Runtime is not deprecated Security · 4 places
Medium Ensure the base image uses a non latest version tag Security · 4 places
Medium Ensure that S3 bucket has a Public Access block Security · 3 places

Ensure that S3 bucket has a Public Access block

Documentation

Where

Medium Ensure that an S3 bucket has a lifecycle configuration Security · 3 places

Ensure that an S3 bucket has a lifecycle configuration

Documentation

Where

Medium Ensure S3 buckets should have event notifications enabled Security · 3 places

Ensure S3 buckets should have event notifications enabled

Documentation

Where

Medium Ensure that S3 bucket has cross-region replication enabled Security · 3 places

Ensure that S3 bucket has cross-region replication enabled

Documentation

Where

Medium Ensure that S3 buckets are encrypted with KMS by default Security · 3 places

Ensure that S3 buckets are encrypted with KMS by default

Documentation

Where

Medium Ensure the S3 bucket has access logging enabled Security · 3 places

Ensure the S3 bucket has access logging enabled

Documentation

Where

Medium Ensure all data stored in the S3 bucket have versioning enabled Reliability · 3 places

Ensure all data stored in the S3 bucket have versioning enabled

Documentation

Where

Medium Ensure IAM policies does not allow write access without constraints Security · 3 places

Ensure IAM policies does not allow write access without constraints

Documentation

Where

Medium Ensure no IAM policies documents allow "*" as a statement's resource for restrictable actions Security · 3 places

Ensure no IAM policies documents allow "*" as a statement's resource for restrictable actions

Documentation

Where

Medium Ensure all data stored in the SQS queue is encrypted Security · 2 places

Ensure all data stored in the SQS queue is encrypted

Documentation

Where

Medium Ensure Postgres RDS as aws_db_instance has Query Logging enabled Security · 1 place

Ensure Postgres RDS as aws_db_instance has Query Logging enabled

Documentation

Where

Medium Ensure RDS instance with copy tags to snapshots is enabled Security · 1 place

Ensure RDS instance with copy tags to snapshots is enabled

Documentation

Where

Medium Ensure that AWS Lambda function is configured inside a VPC Security · 1 place

Ensure that AWS Lambda function is configured inside a VPC

Documentation

Where

Medium Ensure that enhanced monitoring is enabled for Amazon RDS instances Security · 1 place

Ensure that enhanced monitoring is enabled for Amazon RDS instances

Documentation

Where

Medium Ensure that RDS instances have Multi-AZ enabled Reliability · 1 place

Ensure that RDS instances have Multi-AZ enabled

Documentation

Where

Medium Ensure RDS database has IAM authentication enabled Security · 1 place

Ensure RDS database has IAM authentication enabled

Documentation

Where

Medium Ensure DB instance gets all minor upgrades automatically Security · 1 place

Ensure DB instance gets all minor upgrades automatically

Documentation

Where

Medium Ensure every security group and rule has a description Security · 1 place

Ensure every security group and rule has a description

Documentation

Where

Medium Ensure all data stored in the SNS topic is encrypted Security · 1 place

Ensure all data stored in the SNS topic is encrypted

Documentation

Where

Medium Ensure that AWS database instances have deletion protection enabled Reliability · 1 place

Ensure that AWS database instances have deletion protection enabled

Documentation

Where

and 8 more groups with 8 findings

Low 2

Low 1 known vulnerability in gcc-12@12.2.0-14 (postgres:12) Security · 1 CVE

How to fix

No fixed version of gcc-12 is available yet. Check whether postgres:12 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:12) Security · 1 CVE

How to fix

No fixed version of perl is available yet. Check whether postgres:12 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

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.