InfraScan Cloud

Repository scan

developer-portal

pagopa/developer-portal · branch main · scanned 25 Jun 2026 · 390 resources

DOverall
FSecurity
–Reliability · N/A
BCost
352findings · 0 critical, 20 high
$31.23estimated savings per month, from the code

High 36

High 34 known vulnerabilities in openssl@3.5.4-r0 (valkey/valkey:8.1.4-alpine3.22@sha256:e706d1213aaba6896c162bb6a3a9e1894e1a435f28f8f856d14fab2e10aa098b) Security · 34 CVEs

How to fix

Update openssl from 3.5.4-r0 to 3.5.5-r0 or later in valkey/valkey:8.1.4-alpine3.22@sha256:e706d1213aaba6896c162bb6a3a9e1894e1a435f28f8f856d14fab2e10aa098b. 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.5-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-2025-69419 fixed in 3.5.5-r0
  • High CVE-2026-34181 fixed in 3.5.7-r0
  • High CVE-2025-69420 fixed in 3.5.5-r0
  • High CVE-2025-69421 fixed in 3.5.5-r0
  • High CVE-2026-28388 fixed in 3.5.6-r0
  • High CVE-2026-28389 fixed in 3.5.6-r0
  • High CVE-2026-28390 fixed in 3.5.6-r0
  • High CVE-2026-31790 fixed in 3.5.6-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-28387 fixed in 3.5.6-r0
  • High CVE-2026-7383 fixed in 3.5.7-r0
  • High CVE-2025-15467 fixed in 3.5.5-r0
  • High CVE-2026-45447 fixed in 3.5.7-r0
  • High CVE-2026-34182 fixed in 3.5.7-r0
  • High CVE-2026-31789 fixed in 3.5.6-r0
  • Medium CVE-2025-69418 fixed in 3.5.5-r0
  • and 14 more
High 2 known vulnerabilities in musl@1.2.5-r10 (valkey/valkey:8.1.4-alpine3.22@sha256:e706d1213aaba6896c162bb6a3a9e1894e1a435f28f8f856d14fab2e10aa098b) Security · 2 CVEs

How to fix

Update musl from 1.2.5-r10 to 1.2.5-r12 or later in valkey/valkey:8.1.4-alpine3.22@sha256:e706d1213aaba6896c162bb6a3a9e1894e1a435f28f8f856d14fab2e10aa098b. 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.2.5-r12); 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-40200 fixed in 1.2.5-r12
  • Medium CVE-2026-6042 fixed in 1.2.5-r11

Medium 314

Medium Ensure every security group and rule has a description Security · 21 places
Medium Ensure no security groups allow egress from 0.0.0.0:0 to port -1 Security · 15 places
Medium Ensure that CloudWatch Log Group is encrypted by KMS Security · 13 places
Medium Ensure CloudWatch log groups retains logs for at least 1 year Security · 13 places
Medium Ensure that Security Groups are attached to another resource Security · 8 places
Medium Ensure that AWS Lambda function is configured for function-level concurrent execution limit Security · 8 places
Medium Ensure all data stored in the SQS queue is encrypted Security · 8 places
Medium Ensure AWS Lambda function is configured to validate code-signing Security · 8 places
Medium X-Ray tracing is enabled for Lambda Security · 8 places
Medium Ensure AWS API gateway request is validated Security · 7 places
Medium Ensure that AWS Lambda function is configured for a Dead Letter Queue(DLQ) Security · 7 places
Medium Ensure that S3 bucket has cross-region replication enabled Security · 7 places
Medium Ensure that S3 buckets are encrypted with KMS by default Security · 7 places
Medium Check encryption settings for Lambda environmental variable Security · 7 places
Medium Ensure the S3 bucket has access logging enabled Security · 7 places
Medium Ensure S3 buckets should have event notifications enabled Security · 6 places
Medium Ensure all data stored in the S3 bucket have versioning enabled Reliability · 6 places
Medium Ensure CloudFront response header policy enforces Strict Transport Security Security · 6 places
Medium Ensure no IAM policies documents allow "*" as a statement's resource for restrictable actions Security · 6 places
Medium Ensure that an S3 bucket has a lifecycle configuration Security · 5 places
Medium Ensure IAM policies does not allow write access without constraints Security · 5 places
Medium Ensure that AWS Lambda function is configured inside a VPC Security · 4 places
Medium Ensure API Gateway has Access Logging enabled Security · 4 places
Medium 3 known vulnerabilities in busybox@1.37.0-r18 (valkey/valkey:8.1.4-alpine3.22@sha256:e706d1213aaba6896c162bb6a3a9e1894e1a435f28f8f856d14fab2e10aa098b) Security · 3 CVEs

How to fix

No fixed version of busybox is available yet. Check whether valkey/valkey:8.1.4-alpine3.22@sha256:e706d1213aaba6896c162bb6a3a9e1894e1a435f28f8f856d14fab2e10aa098b 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
  • Low CVE-2024-58251 fixed in 1.37.0-r20
  • Low CVE-2025-46394 fixed in 1.37.0-r20
Medium Ensure Domain Name System Security Extensions (DNSSEC) signing is enabled for Amazon Route 53 public hosted zones Security · 3 places
Medium Ensure Domain Name System (DNS) query logging is enabled for Amazon Route 53 hosted zones Security · 3 places
Medium Ensure AWS CloudFront attached WAFv2 WebACL is configured with AMR for Log4j Vulnerability Security · 3 places
Medium Ensure AWS API Gateway endpoints uses client certificate authentication Security · 3 places
Medium Ensure Secrets Manager secrets should have automatic rotation enabled Security · 3 places
Medium Ensure IAM policies does not allow write access without constraints Security · 3 places
Medium Ensure DynamoDB Tables are encrypted using a KMS Customer Managed CMK Security · 3 places
Medium Ensure API Gateway caching is enabled Security · 3 places
Medium Ensure that ECR repositories are encrypted using KMS Security · 3 places
Medium Ensure that Secrets Manager secret is encrypted using KMS CMK Security · 3 places
Medium Ensure Create before destroy for API Gateway Security · 3 places
Medium Ensure DynamoDB point in time recovery (backup) is enabled Reliability · 3 places
Medium Ensure CloudFront distribution has a default root object configured Security · 3 places
Medium Ensure CloudFront distributions should have origin failover configured Security · 3 places
Medium Ensure SSM parameters are using KMS CMK Security · 3 places
Medium Ensure no IAM policies documents allow "*" as a statement's resource for restrictable actions Security · 3 places

and 52 more groups with 77 findings

Low 2

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

Low SQS Max Message Retention Cost · 1 place

SQS queue configured with the maximum 14-day (1209600 s) message retention. On high-volume queues this inflates storage costs and may indicate unprocessed message buildup.

How to fix

Set retention to the minimum business requirement (e.g., 1–4 days for most queues) and alert on queue depth to catch processing failures early.

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.