InfraScan Cloud

Repository scan

icdc-devops

CBIIT/icdc-devops · branch main · scanned 25 Jun 2026 · 933 resources

FOverall
FSecurity
–Reliability · N/A
DCost
1,006findings · 0 critical, 57 high
$718–$1,448estimated savings per month, from the code

High 140

High 68 known vulnerabilities in unknown@unknown (neo4j:enterprise) Security · 68 CVEs

How to fix

No fixed version of unknown is available yet. Check whether neo4j:enterprise 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-48962 fixed in no fix yet
  • High CVE-2026-44892 fixed in no fix yet
  • High CVE-2026-44893 fixed in no fix yet
  • High CVE-2026-44894 fixed in no fix yet
  • High CVE-2026-45416 fixed in no fix yet
  • High CVE-2026-48959 fixed in no fix yet
  • High CVE-2026-50010 fixed in no fix yet
  • High CVE-2026-44249 fixed in no fix yet
  • High CVE-2026-54512 fixed in no fix yet
  • High CVE-2026-54512 fixed in no fix yet
  • High CVE-2026-54513 fixed in no fix yet
  • High CVE-2026-54513 fixed in no fix yet
  • High CVE-2026-45674 fixed in no fix yet
  • High CVE-2026-47691 fixed in no fix yet
  • High CVE-2026-48059 fixed in no fix yet
  • High CVE-2026-49268 fixed in no fix yet
  • High CVE-2026-12087 fixed in no fix yet
  • Medium CVE-2026-45536 fixed in no fix yet
  • Medium CVE-2026-45536 fixed in no fix yet
  • Medium CVE-2025-45582 fixed in no fix yet
  • and 48 more
High 32 known vulnerabilities in curl@7.80.0-r0 (cbiitssrepo/bento-frontend) Security · 32 CVEs

How to fix

Update curl from 7.80.0-r0 to 7.80.0-r1 or later in cbiitssrepo/bento-frontend. 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 7.80.0-r1); 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-27775 fixed in 7.80.0-r1
  • High CVE-2022-27780 fixed in 7.80.0-r2
  • High CVE-2022-27781 fixed in 7.80.0-r2
  • High CVE-2022-27782 fixed in 7.80.0-r2
  • High CVE-2022-42916 fixed in 7.80.0-r4
  • High CVE-2022-43551 fixed in 7.80.0-r5
  • High CVE-2023-28319 fixed in 8.1.0-r0
  • High CVE-2023-38039 fixed in 8.3.0-r0
  • High CVE-2022-22576 fixed in 7.80.0-r1
  • High CVE-2022-42915 fixed in 7.80.0-r4
  • High CVE-2023-27533 fixed in 8.0.1-r0
  • High CVE-2023-27534 fixed in 8.0.1-r0
  • High CVE-2022-32207 fixed in 7.80.0-r2
  • High CVE-2022-32221 fixed in 7.80.0-r4
  • High CVE-2023-38545 fixed in 8.4.0-r0
  • Medium CVE-2022-32205 fixed in 7.80.0-r2
  • Medium CVE-2023-46219 fixed in 8.5.0-r0
  • Medium CVE-2023-27538 fixed in 8.0.1-r0
  • Medium CVE-2022-27774 fixed in 7.80.0-r1
  • Medium CVE-2022-32208 fixed in 7.80.0-r2
  • and 12 more
High 8 known vulnerabilities in openssl@1.1.1l-r7 (cbiitssrepo/bento-frontend) Security · 8 CVEs

How to fix

Update openssl from 1.1.1l-r7 to 1.1.1n-r0 or later in cbiitssrepo/bento-frontend. 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.1.1n-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-2022-0778 fixed in 1.1.1n-r0
  • High CVE-2023-0464 fixed in 1.1.1t-r2
  • Medium CVE-2022-2097 fixed in 1.1.1q-r0
  • Medium CVE-2023-0465 fixed in 1.1.1t-r2
  • Medium CVE-2023-3446 fixed in 1.1.1u-r2
  • Medium CVE-2023-3817 fixed in 1.1.1v-r0
  • Medium CVE-2023-5678 fixed in 1.1.1w-r1
  • Medium CVE-2023-2650 fixed in 1.1.1u-r0
High 7 known vulnerabilities in unknown@unknown (cbiitssrepo/bento-frontend) Security · 7 CVEs

How to fix

No fixed version of unknown is available yet. Check whether cbiitssrepo/bento-frontend 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
  • Medium CVE-2022-4304 fixed in no fix yet
  • Medium CVE-2022-4450 fixed in no fix yet
  • Medium CVE-2023-0215 fixed in no fix yet
  • Medium CVE-2023-23916 fixed in no fix yet
  • Low CVE-2023-23914 fixed in no fix yet
  • Low CVE-2023-23915 fixed in no fix yet
High 5 known vulnerabilities in libxml2@2.9.12-r2 (cbiitssrepo/bento-frontend) Security · 5 CVEs

How to fix

Update libxml2 from 2.9.12-r2 to 2.9.14-r1 or later in cbiitssrepo/bento-frontend. 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 2.9.14-r1); 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-2309 fixed in 2.9.14-r1
  • High CVE-2022-23308 fixed in 2.9.13-r0
  • High CVE-2022-40303 fixed in 2.9.14-r2
  • High CVE-2022-40304 fixed in 2.9.14-r2
  • Medium CVE-2022-29824 fixed in 2.9.14-r0
High 3 known vulnerabilities in freetype@2.11.0-r0 (cbiitssrepo/bento-frontend) Security · 3 CVEs

How to fix

Update freetype from 2.11.0-r0 to 2.11.1-r2 or later in cbiitssrepo/bento-frontend. 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 2.11.1-r2); 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-27405 fixed in 2.11.1-r2
  • High CVE-2022-27406 fixed in 2.11.1-r2
  • High CVE-2022-27404 fixed in 2.11.1-r1
High 3 known vulnerabilities in pcre2@10.39-r0 (cbiitssrepo/bento-frontend) Security · 3 CVEs

How to fix

Update pcre2 from 10.39-r0 to 10.42-r0 or later in cbiitssrepo/bento-frontend. 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 10.42-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-2022-41409 fixed in 10.42-r0
  • High CVE-2022-1586 fixed in 10.40-r0
  • High CVE-2022-1587 fixed in 10.40-r0
High 2 known vulnerabilities in libwebp@1.2.2-r0 (cbiitssrepo/bento-frontend) Security · 2 CVEs

How to fix

Update libwebp from 1.2.2-r0 to 1.2.2-r2 or later in cbiitssrepo/bento-frontend. 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.2-r2); 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-2023-4863 fixed in 1.2.2-r2
  • Medium CVE-2023-1999 fixed in 1.2.2-r1
High 2 known vulnerabilities in ncurses@6.3_p20211120-r0 (cbiitssrepo/bento-frontend) Security · 2 CVEs

How to fix

Update ncurses from 6.3_p20211120-r0 to 6.3_p20211120-r1 or later in cbiitssrepo/bento-frontend. 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 6.3_p20211120-r1); 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-29458 fixed in 6.3_p20211120-r1
  • High CVE-2023-29491 fixed in 6.3_p20211120-r2
High 2 known vulnerabilities in nghttp2@1.46.0-r0 (cbiitssrepo/bento-frontend) Security · 2 CVEs

How to fix

Update nghttp2 from 1.46.0-r0 to 1.46.0-r1 or later in cbiitssrepo/bento-frontend. 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.46.0-r1); 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-2023-35945 fixed in 1.46.0-r1
  • High CVE-2023-44487 fixed in 1.46.0-r2
High 2 known vulnerabilities in xz@5.2.5-r0 (cbiitssrepo/bento-frontend) Security · 2 CVEs

How to fix

Update xz from 5.2.5-r0 to 5.2.5-r1 or later in cbiitssrepo/bento-frontend. 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 5.2.5-r1); 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-1271 fixed in 5.2.5-r1
  • Medium CVE-2020-22916 fixed in no fix yet
High 2 known vulnerabilities in zlib@1.2.11-r3 (cbiitssrepo/bento-frontend) Security · 2 CVEs

How to fix

Update zlib from 1.2.11-r3 to 1.2.12-r0 or later in cbiitssrepo/bento-frontend. 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.12-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-2018-25032 fixed in 1.2.12-r0
  • High CVE-2022-37434 fixed in 1.2.12-r2
High 1 known vulnerability in busybox@1.34.1-r3 (cbiitssrepo/bento-frontend) Security · 1 CVE

How to fix

Update busybox from 1.34.1-r3 to 1.34.1-r5 or later in cbiitssrepo/bento-frontend. 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.34.1-r5); 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-28391 fixed in 1.34.1-r5
High 1 known vulnerability in libretls@3.3.4-r2 (cbiitssrepo/bento-frontend) Security · 1 CVE

How to fix

Update libretls from 3.3.4-r2 to 3.3.4-r3 or later in cbiitssrepo/bento-frontend. 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.4-r3); 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-0778 fixed in 3.3.4-r3
High 1 known vulnerability in libxslt@1.1.34-r1 (cbiitssrepo/bento-frontend) Security · 1 CVE

How to fix

Update libxslt from 1.1.34-r1 to 1.1.35-r0 or later in cbiitssrepo/bento-frontend. 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.1.35-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-2021-30560 fixed in 1.1.35-r0
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 835

Medium Ensure every security group and rule has a description Security · 124 places
Medium Ensure no security groups allow egress from 0.0.0.0:0 to port -1 Security · 35 places
Medium Missing Cost and Usage Report Cost · 27 places
Medium Ensure no IAM policies documents allow "*" as a statement's resource for restrictable actions Security · 24 places
Medium Ensure IAM policies does not allow write access without constraints Security · 23 places
Medium Ensure Instance Metadata Service Version 1 is not enabled Security · 23 places
Medium Ensure IAM policies does not allow permissions management / resource exposure without constraints Security · 21 places
Medium Ensure S3 buckets should have event notifications enabled Security · 19 places
Medium Ensure that S3 bucket has cross-region replication enabled Security · 19 places
Medium Ensure that S3 buckets are encrypted with KMS by default Security · 19 places
Medium Ensure AWS Load Balancer doesn't use HTTP protocol Security · 19 places
Medium Ensure that S3 bucket has a Public Access block Security · 18 places
Medium Ensure that an S3 bucket has a lifecycle configuration Security · 18 places
Medium Ensure Terraform module sources use a commit hash Security · 18 places
Medium Ensure Terraform module sources use a tag with a version number Security · 18 places
Medium Ensure IAM policies does not allow data exfiltration Security · 15 places
Medium Ensure that detailed monitoring is enabled for EC2 instances Security · 15 places
Medium Ensure the S3 bucket has access logging enabled Security · 15 places
Medium Missing Spot Instance Usage Cost · 15 places
Medium Ensure that EC2 is EBS optimized Security · 14 places
Medium Missing S3 Lifecycle Policy Cost · 14 places
Medium Ensure all data stored in the Launch configuration or instance Elastic Blocks Store is securely encrypted Security · 13 places
Medium Ensure all data stored in the S3 bucket have versioning enabled Reliability · 12 places
Medium Ensure that HEALTHCHECK instructions have been added to container images Security · 11 places
Medium Ensure that HTTPS url is used with uri Security · 10 places
Medium Ensure an IAM role is attached to EC2 instance Security · 9 places
Medium Ensure that Security Groups are attached to another resource Security · 9 places
Medium Ensure block is handling task errors properly Security · 8 places
Medium Ensure EC2 Auto Scaling groups use EC2 launch templates Security · 8 places
Medium Ensure that a user for the container has been created Security · 8 places
Medium Ensure AWS Load Balancers use strong ciphers Security · 6 places
Medium Ensure that load balancer is using at least TLS 1.2 Security · 6 places
Medium Ensure that Load Balancer has deletion protection enabled Reliability · 6 places
Medium Ensure that CloudWatch Log Group is encrypted by KMS Security · 6 places
Medium Ensure no security groups allow ingress from 0.0.0.0:0 to port 80 Security · 6 places
Medium Ensure public facing ALB are protected by WAF Security · 5 places
Medium AWS NAT Gateways should be utilized for the default route Security · 5 places
Medium Ensure IAM policies does not allow credentials exposure Security · 5 places
Medium Ensure that AWS Lambda function is configured for function-level concurrent execution limit Security · 5 places
Medium Ensure that AWS Lambda function is configured for a Dead Letter Queue(DLQ) Security · 5 places

and 76 more groups with 179 findings

Low 31

Low Missing AWS Budget Cost · 27 places
Low Large Root Volume Cost · 3 places

Oversized root block device. Many workloads don't require large root volumes.

How to fix

Reduce root volume size to minimum required (typically 8-20 GB for most Linux instances).

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.