Repository scan
single-cell-data-portal
chanzuckerberg/single-cell-data-portal · branch main · scanned 25 Jun 2026 · 19 resources
High 144
High 104 known vulnerabilities in unknown@unknown (postgres:13.0)
How to fix
No fixed version of unknown is available yet. Check whether postgres:13.0 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-2021-33195 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-2020-16845 fixed in no fix yet
- High CVE-2021-27918 fixed in no fix yet
- High CVE-2021-33196 fixed in no fix yet
- High CVE-2021-39293 fixed in no fix yet
- High CVE-2021-41771 fixed in no fix yet
- High CVE-2021-41772 fixed in no fix yet
- High CVE-2022-24921 fixed in no fix yet
- High CVE-2022-27664 fixed in no fix yet
- High CVE-2022-28327 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
- and 84 more
High 21 known vulnerabilities in stdlib@1.13.10 (postgres:13.0)
How to fix
Update stdlib from 1.13.10 to 1.15.13 or later in postgres:13.0. 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.15.13); 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-33198 fixed in 1.15.13
- High CVE-2021-44716 fixed in 1.16.12
- High CVE-2022-23772 fixed in 1.16.14
- 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-2022-29526 fixed in 1.17.10
- Medium CVE-2025-58185 fixed in 1.24.8
- Medium CVE-2021-36221 fixed in 1.15.15
- and 1 more
High 19 known vulnerabilities in unknown@unknown (soluto/oidc-server-mock:0.3.0)
How to fix
No fixed version of unknown is available yet. Check whether soluto/oidc-server-mock:0.3.0 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-2018-0764 fixed in no fix yet
- High CVE-2018-0765 fixed in no fix yet
- High CVE-2018-8292 fixed in no fix yet
- High CVE-2021-1723 fixed in no fix yet
- High CVE-2022-23267 fixed in no fix yet
- High CVE-2022-24464 fixed in no fix yet
- High CVE-2022-29117 fixed in no fix yet
- High CVE-2022-29145 fixed in no fix yet
- High CVE-2022-38013 fixed in no fix yet
- High CVE-2024-21386 fixed in no fix yet
- High CVE-2024-21907 fixed in no fix yet
- High CVE-2023-33170 fixed in no fix yet
- High CVE-2021-26701 fixed in no fix yet
- Medium CVE-2024-39694 fixed in no fix yet
- Medium GHSA-55p7-v223-x366 fixed in no fix yet
- Medium CVE-2022-34716 fixed in no fix yet
- Medium CVE-2022-34716 fixed in no fix yet
- Medium CVE-2024-21319 fixed in no fix yet
- Medium CVE-2024-21319 fixed in no fix yet
Medium 74
Medium Ensure that COPY is used instead of ADD in Dockerfiles
Ensure that COPY is used instead of ADD in Dockerfiles
Where
- ../../Dockerfile.backend:9
- ../../Dockerfile.backend:32
- ../../Dockerfile.backend:33
- ../../Dockerfile.backend:34
- ../../Dockerfile.backend:35
- ../../Dockerfile.wmg_pipeline:6
- ../../Dockerfile.wmg_pipeline:36
- ../../Dockerfile.wmg_pipeline:37
- ../../Dockerfile.wmg_pipeline:38
- ../../Dockerfile.backend_de:9
- ../../Dockerfile.backend_de:34
- ../../Dockerfile.backend_de:35
- ../../Dockerfile.backend_de:36
- ../../Dockerfile.backend_de:37
- ../../Dockerfile.backend_wmg:9
- ../../Dockerfile.backend_wmg:34
- ../../Dockerfile.backend_wmg:35
- ../../Dockerfile.backend_wmg:36
- ../../Dockerfile.backend_wmg:37
- ../../Dockerfile.processing:4
- and 12 more
Medium Ensure that HEALTHCHECK instructions have been added to container images
Ensure that HEALTHCHECK instructions have been added to container images
Where
Medium Ensure that a user for the container has been created
Ensure that a user for the container has been created
Where
Medium Ensure that arrays have a maximum number of items
Ensure that arrays have a maximum number of items
Where
Medium Ensure that the global security field has rules defined
Ensure that the global security field has rules defined
Where
Medium Ensure top-level permissions are not set to write-all
Ensure top-level permissions are not set to write-all
How to fix
See Checkov documentation for remediation guidance.
Where
Medium Ensure that security operations is not empty.
Medium Ensure that APT isn't used
Ensure that APT isn't used
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.