Repository scan
Librarian
jeujai/Librarian · branch main · scanned 25 Jun 2026 · 318 resources
High 325
High 284 known vulnerabilities in unknown@unknown (quay.io/coreos/etcd:v3.5.5)
How to fix
No fixed version of unknown is available yet. Check whether quay.io/coreos/etcd:v3.5.5 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-0286 fixed in no fix yet
- High CVE-2023-47038 fixed in no fix yet
- High CVE-2022-29458 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-2022-1292 fixed in no fix yet
- High CVE-2022-2068 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-2024-2961 fixed in no fix yet
- High CVE-2024-33601 fixed in no fix yet
- High CVE-2026-48962 fixed in no fix yet
- High CVE-2023-0361 fixed in no fix yet
- High CVE-2024-33602 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-2018-25032 fixed in no fix yet
- High CVE-2021-38561 fixed in no fix yet
- High CVE-2021-46828 fixed in no fix yet
- and 264 more
High 16 known vulnerabilities in stdlib@1.16.15 (quay.io/coreos/etcd:v3.5.5)
How to fix
Update stdlib from 1.16.15 to 1.17.9 or later in quay.io/coreos/etcd:v3.5.5. 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.17.9); 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-24675 fixed in 1.17.9
- High CVE-2022-28131 fixed in 1.17.12
- High CVE-2022-30630 fixed in 1.17.12
- High CVE-2022-30632 fixed in 1.17.12
- High CVE-2022-30634 fixed in 1.17.11
- High CVE-2022-30635 fixed in 1.17.12
- High CVE-2022-32189 fixed in 1.17.13
- 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-2024-34155 fixed in 1.22.7
- Medium CVE-2025-58185 fixed in 1.24.8
- Medium CVE-2025-4673 fixed in 1.23.10
High 13 known vulnerabilities in net@0.0.0-20211112202133-69e39bad7dc2 (quay.io/coreos/etcd:v3.5.5)
How to fix
Update net from 0.0.0-20211112202133-69e39bad7dc2 to 0.0.0-20211209124913-491a49abca63 or later in quay.io/coreos/etcd:v3.5.5. 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.0.0-20211209124913-491a49abca63); 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-2021-44716 fixed in 0.0.0-20211209124913-491a49abca63
- High CVE-2026-33814 fixed in 0.53.0
- Medium CVE-2025-22870 fixed in 0.36.0
- Medium CVE-2022-41717 fixed in 0.4.0
- Medium CVE-2024-45338 fixed in 0.33.0
- Medium CVE-2025-47911 fixed in 0.45.0
- Medium CVE-2025-58190 fixed in 0.45.0
- Medium CVE-2026-25681 fixed in 0.55.0
- Medium CVE-2026-27136 fixed in 0.55.0
- Medium CVE-2026-42502 fixed in 0.55.0
- Medium CVE-2026-42506 fixed in 0.55.0
- Medium CVE-2026-25680 fixed in 0.55.0
- Medium CVE-2023-44487 fixed in 0.17.0
High 6 known vulnerabilities in crypto@0.0.0-20220411220226-7b82a4e95df4 (quay.io/coreos/etcd:v3.5.5)
How to fix
Update crypto from 0.0.0-20220411220226-7b82a4e95df4 to 0.35.0 or later in quay.io/coreos/etcd:v3.5.5. 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.35.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-2025-22869 fixed in 0.35.0
- High CVE-2025-47913 fixed in 0.43.0
- High CVE-2026-46597 fixed in 0.52.0
- High CVE-2026-42508 fixed in 0.52.0
- High CVE-2026-46595 fixed in 0.52.0
- Medium CVE-2026-46598 fixed in 0.52.0
High 3 known vulnerabilities in Linux-PAM.mo@unknown (quay.io/coreos/etcd:v3.5.5)
How to fix
No fixed version of Linux-PAM.mo is available yet. Check whether quay.io/coreos/etcd:v3.5.5 needs Linux-PAM.mo 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-6020 fixed in no fix yet
- Medium CVE-2024-22365 fixed in no fix yet
- Medium CVE-2026-54411 fixed in no fix yet
High 1 known vulnerability in e2scrub@.service (quay.io/coreos/etcd:v3.5.5)
How to fix
No fixed version of e2scrub is available yet. Check whether quay.io/coreos/etcd:v3.5.5 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 1 known vulnerability in krb5@1.18.3-6%2Bdeb11u1 (quay.io/coreos/etcd:v3.5.5)
How to fix
Update krb5 from 1.18.3-6%2Bdeb11u1 to 1.18.3-6+deb11u5 or later in quay.io/coreos/etcd:v3.5.5. 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.3-6+deb11u5); 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-2024-37371 fixed in 1.18.3-6+deb11u5
High Expensive NAT Gateway
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 200
Medium Ensure that CloudWatch Log Group is encrypted by KMS
Ensure that CloudWatch Log Group is encrypted by KMS
Where
- ../../archive/infrastructure-backups/main-comprehensive-backup.tf:219
- ../../archive/infrastructure-backups/main-comprehensive-backup.tf:370
- ../../archive/infrastructure-backups/main-comprehensive-backup.tf:381
- ../../archive/infrastructure-backups/main-comprehensive.tf:214
- ../../archive/infrastructure-backups/main-comprehensive.tf:365
- ../../archive/infrastructure-backups/main-comprehensive.tf:376
- ../../infrastructure/aws-native/modules/application/main.tf:81
- ../../infrastructure/aws-native/modules/application/main.tf:88
- ../../infrastructure/aws-native/modules/application/main.tf:447
- ../../infrastructure/aws-native/modules/backup/main.tf:276
- ../../infrastructure/aws-native/modules/databases/main.tf:97
- ../../infrastructure/aws-native/modules/databases/main.tf:198
- ../../infrastructure/aws-native/modules/databases/main.tf:205
- ../../infrastructure/aws-native/modules/databases/main.tf:212
- ../../infrastructure/aws-native/modules/monitoring/container_failure_monitor.tf:124
- ../../infrastructure/aws-native/modules/monitoring/main.tf:28
- ../../infrastructure/aws-native/modules/monitoring/main.tf:35
- ../../infrastructure/aws-native/modules/monitoring/main.tf:42
- ../../infrastructure/aws-native/modules/security/main.tf:594
- ../../infrastructure/aws-native/modules/storage/main.tf:59
- and 1 more
Medium Ensure that Security Groups are attached to another resource
Ensure that Security Groups are attached to another resource
Where
- ../../infrastructure/aws-native/modules/security/main.tf:10
- ../../infrastructure/aws-native/modules/security/main.tf:49
- ../../infrastructure/aws-native/modules/security/main.tf:80
- ../../infrastructure/aws-native/modules/security/main.tf:111
- ../../infrastructure/aws-native/modules/security/main.tf:142
- ../../infrastructure/aws-native/modules/security/main.tf:173
Medium Ensure Secrets Manager secrets should have automatic rotation enabled
Ensure Secrets Manager secrets should have automatic rotation enabled
Where
- ../../archive/infrastructure-backups/main-reconstructed.tf:632
- ../../archive/infrastructure-backups/main-reconstructed.tf:654
- ../../archive/infrastructure-backups/main-reconstructed.tf:676
- ../../infrastructure/aws-native/main.tf:233
- ../../infrastructure/aws-native/main.tf:245
- ../../infrastructure/aws-native/main.tf:257
Medium Ensure S3 buckets should have event notifications enabled
Ensure S3 buckets should have event notifications enabled
Where
- ../../infrastructure/aws-native/main.tf:156
- ../../infrastructure/aws-native/modules/application/main.tf:116
- ../../infrastructure/aws-native/modules/backup/main.tf:15
- ../../infrastructure/aws-native/modules/backup/main.tf:79
- ../../infrastructure/aws-native/modules/databases/main.tf:297
- ../../infrastructure/aws-native/modules/security/main.tf:668
Medium Ensure the S3 bucket has access logging enabled
Ensure the S3 bucket has access logging enabled
Where
- ../../infrastructure/aws-native/main.tf:156
- ../../infrastructure/aws-native/modules/application/main.tf:116
- ../../infrastructure/aws-native/modules/backup/main.tf:15
- ../../infrastructure/aws-native/modules/backup/main.tf:79
- ../../infrastructure/aws-native/modules/databases/main.tf:297
- ../../infrastructure/aws-native/modules/security/main.tf:668
Medium Ensure every security group and rule has a description
Ensure every security group and rule has a description
Where
- ../../infrastructure/aws-native/modules/security/main.tf:10
- ../../infrastructure/aws-native/modules/security/main.tf:49
- ../../infrastructure/aws-native/modules/security/main.tf:80
- ../../infrastructure/aws-native/modules/security/main.tf:111
- ../../infrastructure/aws-native/modules/security/main.tf:142
- ../../infrastructure/aws-native/modules/security/main.tf:173
Medium Ensure AWS Load Balancer doesn't use HTTP protocol
Ensure AWS Load Balancer doesn't use HTTP protocol
Where
- ../../archive/infrastructure-backups/blue-green.tf:22
- ../../archive/infrastructure-backups/blue-green.tf:53
- ../../archive/infrastructure-backups/main-comprehensive-backup.tf:484
- ../../archive/infrastructure-backups/main-comprehensive.tf:479
- ../../archive/infrastructure-backups/main-simplified-backup.tf:265
- ../../infrastructure/aws-native/modules/application/main.tf:170
Medium Ensure no security groups allow egress from 0.0.0.0:0 to port -1
Ensure no security groups allow egress from 0.0.0.0:0 to port -1
Where
- ../../infrastructure/aws-native/modules/security/main.tf:10
- ../../infrastructure/aws-native/modules/security/main.tf:49
- ../../infrastructure/aws-native/modules/security/main.tf:80
- ../../infrastructure/aws-native/modules/security/main.tf:111
- ../../infrastructure/aws-native/modules/security/main.tf:142
- ../../infrastructure/aws-native/modules/security/main.tf:173
Medium Ensure that an S3 bucket has a lifecycle configuration
Ensure that an S3 bucket has a lifecycle configuration
Where
Medium Missing Cost and Usage Report
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 AWS SSM Parameter should be Encrypted
Medium Ensure AWS Neptune cluster deletion protection is enabled
Ensure AWS Neptune cluster deletion protection is enabled
Where
Medium Ensure that S3 bucket has a Public Access block
Medium Ensure that ALB drops HTTP headers
Ensure that ALB drops HTTP headers
Where
Medium Ensure that S3 bucket has cross-region replication enabled
Ensure that S3 bucket has cross-region replication enabled
Where
Medium Ensure that S3 buckets are encrypted with KMS by default
Ensure that S3 buckets are encrypted with KMS by default
Where
Medium Ensure that Load Balancer has deletion protection enabled
Ensure that Load Balancer has deletion protection enabled
Where
Medium Ensure Elasticsearch Domain Audit Logging is enabled
Ensure Elasticsearch Domain Audit Logging is enabled
Where
Medium Ensure Neptune is encrypted by KMS using a customer managed Key (CMK)
Ensure Neptune is encrypted by KMS using a customer managed Key (CMK)
Where
Medium Neptune DB clusters should be configured to copy tags to snapshots
Neptune DB clusters should be configured to copy tags to snapshots
Where
Medium Ensure ECR Image Tags are immutable
Ensure ECR Image Tags are immutable
Where
Medium Load Balancer for Single Instance
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 that ALB redirects HTTP requests into HTTPS ones
Ensure that ALB redirects HTTP requests into HTTPS ones
Where
Medium Ensure public facing ALB are protected by WAF
Ensure public facing ALB are protected by WAF
Where
Medium Ensure that load balancer is using at least TLS 1.2
Ensure that load balancer is using at least TLS 1.2
Where
Medium Ensure VPC subnets do not assign public IP by default
Ensure VPC subnets do not assign public IP by default
Where
Medium Ensure ALB protocol is HTTPS
Medium Ensure all data stored in the S3 bucket have versioning enabled
Ensure all data stored in the S3 bucket have versioning enabled
Where
Medium Ensure Elasticsearch domains are configured with at least three dedicated master nodes for HA
Ensure Elasticsearch domains are configured with at least three dedicated master nodes for HA
Where
Medium Ensure CloudWatch log groups retains logs for at least 1 year
Ensure CloudWatch log groups retains logs for at least 1 year
Where
Medium Ensure no IAM policies documents allow "*" as a statement's resource for restrictable actions
Ensure no IAM policies documents allow "*" as a statement's resource for restrictable actions
Where
Medium Ensure container insights are enabled on ECS cluster
Ensure container insights are enabled on ECS cluster
Where
Medium Ensure the ELBv2 (Application/Network) has access logging enabled
Ensure the ELBv2 (Application/Network) has access logging enabled
Where
Medium Ensure WAF2 has a Logging Configuration
Ensure WAF2 has a Logging Configuration
Where
Medium Ensure that AWS Lambda function is configured for function-level concurrent execution limit
Ensure that AWS Lambda function is configured for function-level concurrent execution limit
Where
Medium Ensure that AWS Lambda function is configured for a Dead Letter Queue(DLQ)
Ensure that AWS Lambda function is configured for a Dead Letter Queue(DLQ)
Where
Medium Ensure that AWS Lambda function is configured inside a VPC
Ensure that AWS Lambda function is configured inside a VPC
Where
Medium Check encryption settings for Lambda environmental variable
Check encryption settings for Lambda environmental variable
Where
Medium Ensure ElastiCache replication group is encrypted by KMS using a customer managed Key (CMK)
Ensure ElastiCache replication group is encrypted by KMS using a customer managed Key (CMK)
Where
Medium Ensure all data stored in the Elasticsearch is encrypted with a CMK
Ensure all data stored in the Elasticsearch is encrypted with a CMK
Where
and 27 more groups with 32 findings
Low 4
Low 1 known vulnerability in pcre3@2%3A8.39-13 (quay.io/coreos/etcd:v3.5.5)
How to fix
No fixed version of pcre3 is available yet. Check whether quay.io/coreos/etcd:v3.5.5 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%2Bdeb11u2 (quay.io/coreos/etcd:v3.5.5)
How to fix
No fixed version of perl is available yet. Check whether quay.io/coreos/etcd:v3.5.5 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 sys@0.0.0-20210615035016-665e8c7367d1 (quay.io/coreos/etcd:v3.5.5)
How to fix
Update sys from 0.0.0-20210615035016-665e8c7367d1 to 0.44.0 or later in quay.io/coreos/etcd:v3.5.5. 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.44.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
- Low CVE-2026-39824 fixed in 0.44.0
Low Unassociated Elastic IP
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.