InfraScan Cloud

Repository scan

authentication-api

govuk-one-login/authentication-api · branch main · scanned 25 Jun 2026 · 603 resources

DOverall
FSecurity
–Reliability · N/A
CCost
985findings · 0 critical, 68 high
$7.47estimated savings per month, from the code

High 123

High 88 known vulnerabilities in unknown@unknown (redis:6.2.19-alpine@sha256:7fe72c486b910f6b1a9769c937dad5d63648ddee82e056f47417542dd40825bb) Security · 88 CVEs

How to fix

No fixed version of unknown is available yet. Check whether redis:6.2.19-alpine@sha256:7fe72c486b910f6b1a9769c937dad5d63648ddee82e056f47417542dd40825bb 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-2023-24539 fixed in no fix yet
  • High CVE-2023-29400 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
  • High CVE-2022-41723 fixed in no fix yet
  • High CVE-2022-41724 fixed in no fix yet
  • High CVE-2022-41725 fixed in no fix yet
  • High CVE-2023-24534 fixed in no fix yet
  • High CVE-2023-24536 fixed in no fix yet
  • High CVE-2023-24537 fixed in no fix yet
  • High CVE-2023-39325 fixed in no fix yet
  • High CVE-2023-44487 fixed in no fix yet
  • and 68 more
High 19 known vulnerabilities in openssl@3.3.4-r0 (redis:6.2.19-alpine@sha256:7fe72c486b910f6b1a9769c937dad5d63648ddee82e056f47417542dd40825bb) Security · 19 CVEs

How to fix

Update openssl from 3.3.4-r0 to 3.3.6-r0 or later in redis:6.2.19-alpine@sha256:7fe72c486b910f6b1a9769c937dad5d63648ddee82e056f47417542dd40825bb. 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.3.6-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.3.6-r0
  • High CVE-2025-69420 fixed in 3.3.6-r0
  • High CVE-2025-69421 fixed in 3.3.6-r0
  • High CVE-2025-9230 fixed in 3.3.5-r0
  • High CVE-2026-28388 fixed in 3.3.7-r0
  • High CVE-2026-28389 fixed in 3.3.7-r0
  • High CVE-2026-28390 fixed in 3.3.7-r0
  • High CVE-2026-31790 fixed in 3.3.7-r0
  • High CVE-2026-28387 fixed in 3.3.7-r0
  • High CVE-2025-15467 fixed in 3.3.6-r0
  • High CVE-2026-31789 fixed in 3.3.7-r0
  • Medium CVE-2025-69418 fixed in 3.3.6-r0
  • Medium CVE-2025-68160 fixed in 3.3.6-r0
  • Medium CVE-2026-22796 fixed in 3.3.6-r0
  • Medium CVE-2026-22795 fixed in 3.3.6-r0
  • Medium CVE-2025-15468 fixed in 3.3.6-r0
  • Medium CVE-2025-66199 fixed in 3.3.6-r0
  • Medium CVE-2025-9232 fixed in 3.3.5-r0
  • Medium CVE-2025-9231 fixed in 3.3.5-r0
High 14 known vulnerabilities in stdlib@1.18.2 (redis:6.2.19-alpine@sha256:7fe72c486b910f6b1a9769c937dad5d63648ddee82e056f47417542dd40825bb) Security · 14 CVEs

How to fix

Update stdlib from 1.18.2 to 1.18.4 or later in redis:6.2.19-alpine@sha256:7fe72c486b910f6b1a9769c937dad5d63648ddee82e056f47417542dd40825bb. 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 2 known vulnerabilities in musl@1.2.5-r9 (redis:6.2.19-alpine@sha256:7fe72c486b910f6b1a9769c937dad5d63648ddee82e056f47417542dd40825bb) Security · 2 CVEs

How to fix

Update musl from 1.2.5-r9 to 1.2.5-r11 or later in redis:6.2.19-alpine@sha256:7fe72c486b910f6b1a9769c937dad5d63648ddee82e056f47417542dd40825bb. 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-r11); 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-r11
  • Medium CVE-2026-6042 fixed in 1.2.5-r10

Medium 851

Medium Ensure that AWS Lambda function is configured for a Dead Letter Queue(DLQ) Security · 112 places
Medium Ensure that AWS Lambda function is configured for function-level concurrent execution limit Security · 109 places
Medium Ensure IAM policies does not allow write access without constraints Security · 76 places
Medium Ensure no IAM policies documents allow "*" as a statement's resource for restrictable actions Security · 71 places
Medium Check encryption settings for Lambda environment variable Security · 67 places

Check encryption settings for Lambda environment variable

Documentation

Where

Medium Ensure that AWS Lambda function permissions delegated to AWS services are limited by SourceArn or SourceAccount Security · 60 places

Ensure that AWS Lambda function permissions delegated to AWS services are limited by SourceArn or SourceAccount

Documentation

Where

Medium Base64 High Entropy String Security · 58 places
Medium Ensure CloudWatch log groups retains logs for at least 1 year Security · 52 places
Medium Ensure top-level permissions are not set to write-all Security · 25 places
Medium Ensure AWS API gateway request is validated Security · 17 places
Medium Ensure IAM policies does not allow permissions management / resource exposure without constraints Security · 17 places
Medium AWS SSM Parameter should be Encrypted Security · 15 places
Medium Ensure no hard-coded secrets exist in Lambda environment Security · 13 places
Medium Ensure API Gateway caching is enabled Security · 10 places
Medium Ensure the S3 bucket has access logging enabled Security · 10 places
Medium Ensure that the global security field has rules defined Security · 8 places
Medium X-Ray tracing is enabled for Lambda Security · 7 places
Medium Ensure there is no open access to back-end resources through API Security · 6 places
Medium Lambda Over-Provisioned Memory Cost · 6 places

Lambda function with memory >= 3008 MB (the old Lambda maximum, a common cargo-cult setting). Lambda pricing scales linearly with memory; over-provisioning directly inflates costs.

How to fix

Profile the function with AWS Lambda Power Tuning and reduce memory to the minimum needed. Most functions run fine at 256–1024 MB.

Where

Medium Ensure that an S3 bucket has a lifecycle configuration Security · 5 places
Medium Ensure that AWS Lambda function is configured inside a VPC Security · 5 places
Medium Ensure that S3 bucket has cross-region replication enabled Security · 5 places
Medium Ensure that Secrets Manager secret is encrypted using KMS CMK Security · 5 places
Medium Missing S3 Lifecycle Policy Cost · 5 places

S3 bucket without lifecycle rules. Objects are retained indefinitely, increasing storage costs.

How to fix

Define lifecycle rules to transition objects to cheaper storage classes (e.g., Glacier) or delete them after a retention period.

Where

Medium Missing Cost and Usage Report Cost · 5 places

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 Ensure AWS SQS uses CMK not AWS default keys for encryption Security · 4 places
Medium Check encryption settings for Lambda environmental variable Security · 4 places
Medium Ensure every security group and rule has a description Security · 4 places
Medium Ensure AWS Lambda function is configured to validate code-signing Security · 4 places
Medium Ensure that arrays have a maximum number of items Security · 4 places
Medium 3 known vulnerabilities in busybox@1.37.0-r12 (redis:6.2.19-alpine@sha256:7fe72c486b910f6b1a9769c937dad5d63648ddee82e056f47417542dd40825bb) Security · 3 CVEs

How to fix

No fixed version of busybox is available yet. Check whether redis:6.2.19-alpine@sha256:7fe72c486b910f6b1a9769c937dad5d63648ddee82e056f47417542dd40825bb 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-r14
  • Low CVE-2025-46394 fixed in 1.37.0-r14
Medium Ensure that Security Groups are attached to another resource Security · 3 places
Medium Ensure S3 buckets should have event notifications enabled Security · 3 places
Medium Ensure KMS key Policy is defined Security · 3 places
Medium Ensure ElastiCache replication group is encrypted by KMS using a customer managed Key (CMK) Security · 3 places

Ensure ElastiCache replication group is encrypted by KMS using a customer managed Key (CMK)

Documentation

Where

Medium Ensure all data stored in the SNS topic is encrypted Security · 3 places
Medium Ensure that API keys are not sent over cleartext Security · 3 places
Medium API Gateway REST Instead of HTTP API Cost · 3 places

aws_api_gateway_rest_api (REST API) costs ~3.5x more per million requests than aws_apigatewayv2_api (HTTP API). Most modern use cases are supported by the HTTP API.

How to fix

Migrate to aws_apigatewayv2_api (HTTP API v2) unless REST-specific features (usage plans, request validation, custom authorizers v1) are required.

Where

Medium 2 known vulnerabilities in zlib@1.3.1-r2 (redis:6.2.19-alpine@sha256:7fe72c486b910f6b1a9769c937dad5d63648ddee82e056f47417542dd40825bb) Security · 2 CVEs

How to fix

Update zlib from 1.3.1-r2 to 1.3.2-r0 or later in redis:6.2.19-alpine@sha256:7fe72c486b910f6b1a9769c937dad5d63648ddee82e056f47417542dd40825bb. 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.3.2-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

  • Medium CVE-2026-22184 fixed in 1.3.2-r0
  • Low CVE-2026-27171 fixed in 1.3.2-r0
Medium Ensure public API gateway are protected by WAF Security · 2 places

and 19 more groups with 34 findings

Low 11

Low SQS Max Message Retention Cost · 6 places

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

Low Missing AWS Budget Cost · 5 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

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.