chore(findings): ccj2-a3im/datahub/datahub-gms
Summary
ccj2-a3im/datahub/datahub-gms has 43 new findings discovered during continuous monitoring.
More information can be found in the VAT located here: https://vat.dso.mil/vat/image?imageName=ccj2-a3im/datahub/datahub-gms&tag=1.0.0&branch=master
| id | source | severity | package | impact | workaround |
|---|---|---|---|---|---|
| CVE-2012-5783 | Anchore CVE | Medium | commons-httpclient-3.1 | ||
| CVE-2014-3488 | Anchore CVE | Medium | grpc-netty-1.69.0 | ||
| CVE-2015-2156 | Anchore CVE | High | grpc-netty-1.69.0 | ||
| CVE-2019-16869 | Anchore CVE | High | grpc-netty-1.69.0 | ||
| CVE-2020-13956 | Anchore CVE | Medium | commons-httpclient-3.1 | ||
| CVE-2021-21290 | Anchore CVE | Medium | grpc-netty-1.69.0 | ||
| CVE-2021-21295 | Anchore CVE | Medium | grpc-netty-1.69.0 | ||
| CVE-2021-21409 | Anchore CVE | Medium | grpc-netty-1.69.0 | ||
| CVE-2021-26291 | Anchore CVE | Critical | maven-artifact-3.6.3 | ||
| CVE-2021-37136 | Anchore CVE | High | grpc-netty-1.69.0 | ||
| CVE-2021-37137 | Anchore CVE | High | grpc-netty-1.69.0 | ||
| CVE-2021-43797 | Anchore CVE | Medium | grpc-netty-1.69.0 | ||
| CVE-2022-24823 | Anchore CVE | Medium | grpc-netty-1.69.0 | ||
| CVE-2022-41881 | Anchore CVE | High | grpc-netty-1.69.0 | ||
| CVE-2023-28115 | Twistlock CVE | Critical | snappy-1.1.10-r2 | ||
| CVE-2023-34462 | Anchore CVE | Medium | grpc-netty-1.69.0 | ||
| CVE-2023-35116 | Anchore CVE | Medium | jackson-databind-2.15.4 | ||
| CVE-2023-3635 | Anchore CVE | High | okio-fakefilesystem-jvm-3.2.0 | ||
| CVE-2023-41330 | Twistlock CVE | Critical | snappy-1.1.10-r2 | ||
| CVE-2024-12798 | Twistlock CVE | Medium | ch.qos.logback_logback-core-1.4.14 | ||
| CVE-2024-12801 | Twistlock CVE | Low | ch.qos.logback_logback-core-1.4.14 | ||
| CVE-2024-36124 | Twistlock CVE | Medium | org.iq80.snappy_snappy-0.4 | ||
| CVE-2024-39657 | Anchore CVE | High | opentelemetry-exporter-sender-okhttp-1.45.0 | ||
| CVE-2024-43126 | Anchore CVE | High | opentelemetry-exporter-sender-okhttp-1.45.0 | ||
| CVE-2024-45338 | Anchore CVE | Medium | golang.org/x/net-v0.32.0 | ||
| CVE-2024-47535 | Anchore CVE | Medium | grpc-netty-1.69.0 | ||
| CVE-2024-50379 | Anchore CVE | Critical | tomcat-embed-el-10.1.28 | ||
| CVE-2024-52316 | Anchore CVE | Critical | tomcat-embed-el-10.1.28 | ||
| CVE-2024-52317 | Anchore CVE | Medium | tomcat-embed-el-10.1.28 | ||
| CVE-2024-54677 | Anchore CVE | Medium | tomcat-embed-el-10.1.28 | ||
| CVE-2024-56337 | Anchore CVE | Critical | tomcat-embed-el-10.1.28 | ||
| CVE-2025-22871 | Anchore CVE | Critical | stdlib-go1.24.1 | ||
| CVE-2025-22871 | Twistlock CVE | Low | net/http/internal-1.24.1 | ||
| CVE-2025-24813 | Anchore CVE | Critical | tomcat-embed-el-10.1.28 | ||
| CVE-2025-25193 | Anchore CVE | Medium | grpc-netty-1.69.0 | ||
| CVE-2025-25193 | Anchore CVE | Medium | grpc-netty-shaded-1.69.0 | ||
| GHSA-6v67-2wr5-gvf4 | Anchore CVE | Low | logback-core-1.4.14 | ||
| GHSA-8wh2-6qhj-h7j9 | Anchore CVE | Medium | snappy-0.4 | ||
| GHSA-hcg3-q754-cr77 | Anchore CVE | High | golang.org/x/crypto-v0.31.0 | ||
| GHSA-pr98-23f8-jwxv | Anchore CVE | Medium | logback-core-1.4.14 | ||
| GHSA-qxp5-gwg8-xv66 | Anchore CVE | Medium | golang.org/x/net-v0.32.0 | ||
| GHSA-vvgc-356p-c3xw | Anchore CVE | Medium | golang.org/x/net-v0.32.0 | ||
| d33cd1c56d51b8a0593f5ec64f2fc68e | Anchore Compliance | Critical |
More information can be found in the VAT located here: https://vat.dso.mil/vat/image?imageName=ccj2-a3im/datahub/datahub-gms&tag=1.0.0&branch=master
Tasks
Contributor:
-
Provide justifications for findings in the VAT (docs) -
Apply the StatusVerification label to this issue and wait for feedback
Iron Bank:
-
Review findings and justifications
Note: If the above process is rejected for any reason, the
Verificationlabel will be removed and the issue will be sent back toOpen. Any comments will be listed in this issue for you to address. Once they have been addressed, you must re-add theVerificationlabel.
Questions?
Contact the Iron Bank team by commenting on this issue with your questions or concerns. If you do not receive a response, add /cc @ironbank-notifications/onboarding.
Additionally, Iron Bank hosts an AMA working session every Wednesday from 1630-1730EST to answer questions.