InfraScan Cloud

Repository scan

teachLink_backend

rinafcode/teachLink_backend · branch main · scanned 25 Jun 2026 · 120 resources

DOverall
FSecurity
–Reliability · N/A
BCost
316findings · 0 critical, 14 high
$4.65–$51.00estimated savings per month, from the code

High 27

High 23 known vulnerabilities in unknown@unknown (prom/prometheus:latest) Security · 23 CVEs

How to fix

No fixed version of unknown is available yet. Check whether prom/prometheus:latest 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-41567 fixed in no fix yet
  • High CVE-2026-42306 fixed in no fix yet
  • High CVE-2026-39829 fixed in no fix yet
  • High CVE-2026-42154 fixed in no fix yet
  • High CVE-2026-34040 fixed in no fix yet
  • High CVE-2026-39830 fixed in no fix yet
  • High CVE-2026-39831 fixed in no fix yet
  • High CVE-2026-39832 fixed in no fix yet
  • High CVE-2026-39833 fixed in no fix yet
  • High CVE-2026-39834 fixed in no fix yet
  • High CVE-2026-46595 fixed in no fix yet
  • Medium CVE-2026-44903 fixed in no fix yet
  • Medium CVE-2025-11065 fixed in no fix yet
  • Medium CVE-2026-39835 fixed in no fix yet
  • Medium CVE-2026-40179 fixed in no fix yet
  • Medium GHSA-2464-8j7c-4cjm fixed in no fix yet
  • Medium CVE-2020-8911 fixed in no fix yet
  • Medium CVE-2026-41568 fixed in no fix yet
  • Medium CVE-2026-39828 fixed in no fix yet
  • Medium CVE-2026-39827 fixed in no fix yet
  • and 3 more
High 3 known vulnerabilities in crypto@0.51.0 (prom/prometheus:latest) Security · 3 CVEs

How to fix

Update crypto from 0.51.0 to 0.52.0 or later in prom/prometheus:latest. 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 0.52.0); 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-46597 fixed in 0.52.0
  • High CVE-2026-42508 fixed in 0.52.0
  • Medium CVE-2026-46598 fixed in 0.52.0
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 284

Medium The default namespace should not be used Security · 16 places
Medium Ensure that Security Groups are attached to another resource Security · 12 places
Medium Ensure every security group and rule has a description Security · 12 places
Medium Ensure no security groups allow egress from 0.0.0.0:0 to port -1 Security · 12 places
Medium Ensure S3 buckets should have event notifications enabled Security · 9 places
Medium Ensure that S3 bucket has cross-region replication enabled Security · 9 places
Medium Ensure that S3 buckets are encrypted with KMS by default Security · 9 places
Medium Ensure that CloudWatch Log Group is encrypted by KMS Security · 9 places
Medium Ensure the S3 bucket has access logging enabled Security · 9 places
Medium Ensure CloudWatch log groups retains logs for at least 1 year Security · 9 places
Medium Base64 High Entropy String Security · 8 places
Medium Ensure that an S3 bucket has a lifecycle configuration Security · 6 places
Medium Ensure VPC subnets do not assign public IP by default Security · 6 places
Medium Use read-only filesystem for containers where possible Security · 5 places
Medium Ensure that the seccomp profile is set to docker/default or runtime/default Security · 5 places
Medium Ensure that Service Account Tokens are only mounted where necessary Security · 5 places
Medium Containers should run as a high UID to avoid host conflict Security · 5 places
Medium Image should use digest Security · 5 places
Medium Ensure all data stored in the SQS queue is encrypted Security · 4 places
Medium Image Pull Policy should be Always Security · 4 places
Medium Containers should not run with allowPrivilegeEscalation Security · 4 places
Medium Minimize the admission of root containers Security · 4 places
Medium Minimize the admission of containers with the NET_RAW capability Security · 4 places
Medium Apply security context to your pods and containers Security · 4 places
Medium Apply security context to your containers Security · 4 places
Medium Minimize the admission of containers with capabilities assigned Security · 4 places
Medium Ensure VPC flow logging is enabled in all VPCs Security · 3 places
Medium Ensure the default security group of every VPC restricts all traffic Security · 3 places
Medium Ensure that ALB redirects HTTP requests into HTTPS ones Security · 3 places
Medium Ensure public facing ALB are protected by WAF Security · 3 places
Medium Ensure RDS instance with copy tags to snapshots is enabled Security · 3 places
Medium Ensure top-level permissions are not set to write-all Security · 3 places

Ensure top-level permissions are not set to write-all

How to fix

See Checkov documentation for remediation guidance.

Where

Medium Minimize the admission of pods which lack an associated NetworkPolicy Security · 3 places

Minimize the admission of pods which lack an associated NetworkPolicy

How to fix

See Checkov documentation for remediation guidance.

Where

Medium Ensure that load balancer is using at least TLS 1.2 Security · 3 places
Medium Ensure that enhanced monitoring is enabled for Amazon RDS instances Security · 3 places
Medium Ensure that ALB drops HTTP headers Security · 3 places
Medium Ensure that Amazon ElastiCache Redis clusters have automatic backup turned on Reliability · 3 places

Ensure that Amazon ElastiCache Redis clusters have automatic backup turned on

Documentation

Where

Medium Ensure that Load Balancer has deletion protection enabled Reliability · 3 places
Medium Ensure that RDS instances have Multi-AZ enabled Reliability · 3 places
Medium Ensure ALB protocol is HTTPS Security · 3 places

and 28 more groups with 59 findings

Low 5

Low Missing AWS Budget Cost · 2 places

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 Cost · 2 places

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

Low Unassociated Elastic IP Cost · 1 place

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

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.