InfraScan Cloud

Repository scan

PLATEAU-SNAP-Server

Project-PLATEAU/PLATEAU-SNAP-Server · branch main · scanned 25 Jun 2026 · 145 resources

DOverall
FSecurity
–Reliability · N/A
BCost
647findings · 0 critical, 136 high
$25.00–$91.35estimated savings per month, from the code

High 510

High 480 known vulnerabilities in unknown@unknown (postgis/postgis:16-3.4) Security · 480 CVEs

How to fix

No fixed version of unknown is available yet. Check whether postgis/postgis:16-3.4 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-2025-64720 fixed in no fix yet
  • High CVE-2025-65018 fixed in no fix yet
  • High CVE-2025-66293 fixed in no fix yet
  • High CVE-2026-32741 fixed in no fix yet
  • High CVE-2026-32882 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-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-2026-49014 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
  • and 460 more
High 14 known vulnerabilities in aa_ER@saaho (postgis/postgis:16-3.4) Security · 14 CVEs

How to fix

No fixed version of aa_ER is available yet. Check whether postgis/postgis:16-3.4 needs aa_ER 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-15281 fixed in no fix yet
  • High CVE-2026-0915 fixed in no fix yet
  • High CVE-2026-4046 fixed in no fix yet
  • High CVE-2025-4802 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-2025-0395 fixed in no fix yet
  • Low CVE-2010-4756 fixed in no fix yet
  • Low CVE-2018-20796 fixed in no fix yet
  • Low CVE-2019-1010022 fixed in no fix yet
  • Low CVE-2019-1010023 fixed in no fix yet
  • Low CVE-2019-1010024 fixed in no fix yet
  • Low CVE-2019-1010025 fixed in no fix yet
  • Low CVE-2019-9192 fixed in no fix yet
High 14 known vulnerabilities in stdlib@1.18.2 (postgis/postgis:16-3.4) Security · 14 CVEs

How to fix

Update stdlib from 1.18.2 to 1.18.4 or later in postgis/postgis:16-3.4. 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 1 known vulnerability in e2scrub@.service (postgis/postgis:16-3.4) Security · 1 CVE

How to fix

No fixed version of e2scrub is available yet. Check whether postgis/postgis:16-3.4 needs e2scrub 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-2022-1304 fixed in no fix yet
High Expensive NAT Gateway Cost · 1 place

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 116

Medium Ensure every security group and rule has a description Security · 22 places
Medium Ensure no security groups allow egress from 0.0.0.0:0 to port -1 Security · 5 places
Medium Ensure that ECR repositories are encrypted using KMS Security · 4 places
Medium Ensure that CloudWatch Log Group is encrypted by KMS Security · 4 places
Medium Ensure CloudWatch log groups retains logs for at least 1 year Security · 4 places
Medium Ensure AWS Load Balancer doesn't use HTTP protocol Security · 4 places
Medium Ensure ECR Image Tags are immutable Security · 4 places
Medium Ensure that all EIP addresses allocated to a VPC are attached to EC2 instances Security · 2 places

Ensure that all EIP addresses allocated to a VPC are attached to EC2 instances

Documentation

Where

Medium Ensure public facing ALB are protected by WAF Security · 2 places
Medium Ensure Domain Name System Security Extensions (DNSSEC) signing is enabled for Amazon Route 53 public hosted zones Security · 2 places

Ensure Domain Name System Security Extensions (DNSSEC) signing is enabled for Amazon Route 53 public hosted zones

Documentation

Where

Medium Ensure Domain Name System (DNS) query logging is enabled for Amazon Route 53 hosted zones Security · 2 places

Ensure Domain Name System (DNS) query logging is enabled for Amazon Route 53 hosted zones

Documentation

Where

Medium Ensure Secrets Manager secrets should have automatic rotation enabled Security · 2 places
Medium Ensure KMS key Policy is defined Security · 2 places
Medium Ensure that load balancer is using at least TLS 1.2 Security · 2 places

Ensure that load balancer is using at least TLS 1.2

Documentation

Where

Medium Ensure that AWS Lambda function is configured for function-level concurrent execution limit Security · 2 places

Ensure that AWS Lambda function is configured for function-level concurrent execution limit

Documentation

Where

Medium Ensure that AWS Lambda function is configured for a Dead Letter Queue(DLQ) Security · 2 places

Ensure that AWS Lambda function is configured for a Dead Letter Queue(DLQ)

Documentation

Where

Medium Ensure that ALB drops HTTP headers Security · 2 places
Medium Ensure that Secrets Manager secret is encrypted using KMS CMK Security · 2 places
Medium Ensure that Load Balancer has deletion protection enabled Reliability · 2 places

Ensure that Load Balancer has deletion protection enabled

Documentation

Where

Medium Check encryption settings for Lambda environmental variable Security · 2 places
Medium Ensure no security groups allow ingress from 0.0.0.0:0 to port 80 Security · 2 places
Medium Ensure AWS Lambda function is configured to validate code-signing Security · 2 places

Ensure AWS Lambda function is configured to validate code-signing

Documentation

Where

Medium Ensure ECS containers are limited to read-only access to root filesystems Security · 2 places

Ensure ECS containers are limited to read-only access to root filesystems

Documentation

Where

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

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

Documentation

Where

Medium Ensure rotation for customer created CMKs is enabled Security · 2 places
Medium Ensure the ELBv2 (Application/Network) has access logging enabled Security · 2 places

Ensure the ELBv2 (Application/Network) has access logging enabled

Documentation

Where

Medium Load Balancer for Single Instance Cost · 2 places

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

Medium Ensure VPC flow logging is enabled in all VPCs Security · 1 place

Ensure VPC flow logging is enabled in all VPCs

Documentation

Where

Medium Ensure the default security group of every VPC restricts all traffic Security · 1 place

Ensure the default security group of every VPC restricts all traffic

Documentation

Where

Medium Ensure that ALB redirects HTTP requests into HTTPS ones Security · 1 place

Ensure that ALB redirects HTTP requests into HTTPS ones

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 that S3 bucket has a Public Access block Security · 1 place

Ensure that S3 bucket has a Public Access block

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 S3 buckets should have event notifications enabled Security · 1 place

Ensure S3 buckets should have event notifications enabled

Documentation

Where

Medium Ensure AWS Load Balancers use strong ciphers Security · 1 place

Ensure AWS Load Balancers use strong ciphers

Documentation

Where

Medium Ensure IAM policies does not allow write access without constraints Security · 1 place

Ensure IAM policies does not allow write access without constraints

Documentation

Where

Medium Ensure that detailed monitoring is enabled for EC2 instances Security · 1 place

Ensure that detailed monitoring is enabled for EC2 instances

Documentation

Where

Medium Ensure that respective logs of Amazon Relational Database Service (Amazon RDS) are enabled Security · 1 place

Ensure that respective logs of Amazon Relational Database Service (Amazon RDS) are enabled

Documentation

Where

Medium Ensure that EC2 is EBS optimized Security · 1 place

Ensure that EC2 is EBS optimized

Documentation

Where

Medium Ensure that S3 bucket has cross-region replication enabled Security · 1 place

Ensure that S3 bucket has cross-region replication enabled

Documentation

Where

and 16 more groups with 16 findings

Low 21

Low 10 known vulnerabilities in hdf5@1.10.6%2Brepack-4%2Bdeb11u1 (postgis/postgis:16-3.4) Security · 10 CVEs

How to fix

No fixed version of hdf5 is available yet. Check whether postgis/postgis:16-3.4 needs hdf5 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-2018-14031 fixed in no fix yet
  • Low CVE-2018-14034 fixed in no fix yet
  • Low CVE-2018-14035 fixed in no fix yet
  • Low CVE-2018-16438 fixed in no fix yet
  • Low CVE-2020-18232 fixed in no fix yet
  • Low CVE-2020-18494 fixed in no fix yet
  • Low CVE-2021-45829 fixed in no fix yet
  • Low CVE-2024-32614 fixed in no fix yet
  • Low CVE-2025-44904 fixed in no fix yet
  • Low CVE-2025-44905 fixed in no fix yet
Low 2 known vulnerabilities in giflib@5.1.9-2 (postgis/postgis:16-3.4) Security · 2 CVEs

How to fix

No fixed version of giflib is available yet. Check whether postgis/postgis:16-3.4 needs giflib 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-28506 fixed in no fix yet
  • Low CVE-2023-39742 fixed in no fix yet
Low 2 known vulnerabilities in tiff@4.2.0-1%2Bdeb11u5 (postgis/postgis:16-3.4) Security · 2 CVEs

How to fix

No fixed version of tiff is available yet. Check whether postgis/postgis:16-3.4 needs tiff 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-2018-10126 fixed in no fix yet
  • Low CVE-2024-6716 fixed in no fix yet
Low 1 known vulnerability in freetype@2.10.4%2Bdfsg-1%2Bdeb11u1 (postgis/postgis:16-3.4) Security · 1 CVE

How to fix

No fixed version of freetype is available yet. Check whether postgis/postgis:16-3.4 needs freetype 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-31782 fixed in no fix yet
Low 1 known vulnerability in pcre3@2%3A8.39-13 (postgis/postgis:16-3.4) Security · 1 CVE

How to fix

No fixed version of pcre3 is available yet. Check whether postgis/postgis:16-3.4 needs pcre3 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-2017-11164 fixed in no fix yet
Low 1 known vulnerability in perl@5.32.1-4%2Bdeb11u3 (postgis/postgis:16-3.4) Security · 1 CVE

How to fix

No fixed version of perl is available yet. Check whether postgis/postgis:16-3.4 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 1 known vulnerability in poppler@20.09.0-3.1%2Bdeb11u1 (postgis/postgis:16-3.4) Security · 1 CVE

How to fix

No fixed version of poppler is available yet. Check whether postgis/postgis:16-3.4 needs poppler 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-2013-4472 fixed in no fix yet
Low 1 known vulnerability in sqlite3@3.34.1-3 (postgis/postgis:16-3.4) Security · 1 CVE

How to fix

No fixed version of sqlite3 is available yet. Check whether postgis/postgis:16-3.4 needs sqlite3 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-2025-52099 fixed in no fix yet
Low 1 known vulnerability in xerces-c@3.2.3%2Bdebian-3%2Bdeb11u1 (postgis/postgis:16-3.4) Security · 1 CVE

How to fix

No fixed version of xerces-c is available yet. Check whether postgis/postgis:16-3.4 needs xerces-c 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-2012-0880 fixed in no fix yet
Low Missing AWS Budget Cost · 1 place

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.