chore(findings): opensource/metabase/metabase
Summary
opensource/metabase/metabase has 2 new findings discovered during continuous monitoring.
More information can be found in the VAT located here: https://vat.dso.mil/vat/image?imageName=opensource/metabase/metabase&tag=v0.53.9&branch=master
| id | source | severity | package | impact | workaround |
|---|---|---|---|---|---|
| CVE-2022-37967 | Anchore CVE | High | krb5-libs-1.21.1-4.el9_5 | ||
| CVE-2025-25193 | Twistlock CVE | Medium | io.netty_netty-common-4.1.115.Final |
More information can be found in the VAT located here: https://vat.dso.mil/vat/image?imageName=opensource/metabase/metabase&tag=v0.53.9&branch=master
Novel Tidelift Findings (Experimental)
opensource/metabase/metabase has 8 novel Tidelift findings discovered during continuous monitoring.
NOTE: This table is for Iron Bank evaluation and testing purposes. No action required by vendors.
| id | cvss score | package | impact | workaround |
|---|---|---|---|---|
| CVE-2020-36843 | 4.3 | pkg:maven/net.i2p.crypto/eddsa@0.3.0 | ||
| CVE-2023-2976 | 7.1 | pkg:maven/com.google.guava/guava@30.1.1-jre | ||
| CVE-2024-23944 | 5.3 | pkg:maven/org.apache.zookeeper/zookeeper@3.8.3 | ||
| CVE-2024-29131 | 7.3 | pkg:maven/org.apache.commons/commons-configuration2@2.8.0 | If you use a Path object with the noted APIs, you will run into this issue. | |
| CVE-2024-29133 | 5.4 | pkg:maven/org.apache.commons/commons-configuration2@2.8.0 | Encountering this issue would require an applications code path to run this method with a cyclical object graph which would not normally happen when processing a configuration file here. | |
| CVE-2024-6763 | 3.7 | pkg:maven/org.eclipse.jetty/jetty-http@11.0.24 | If using the Jetty internal HttpURI as part of Jetty server and Jetty client you are not vulnerable.If using HttpURI in your application directly, then you are vulnerable if you use the results of HttpURI to apply filtering based on the given URI. | |
| CVE-2025-24970 | 7.5 | pkg:maven/io.netty/netty-handler@4.1.116.Final | This is a critical vulnerability that can crash your application very easily, just by sending a crafted packet. Upgrade or workaround is highly recommended. | First option Disable native TLS support by removing the nettytcnative dependency or explicitly telling Netty not to use native TLS support. This may degrade your applications TLS performance.Second option Change the code fromSslContext context ...SslHandler handler context.newHandler....toSslContext context ...SSLEngine engine context.newEngine....SslHandler handler new SslHandlerengine, .... |
| CVE-2025-25193 | 5.5 | pkg:maven/io.netty/netty-common@4.1.115.Final | This vulnerability can be triggered only when an attacker already has the write access to the filesystem. In addition, an attacker must create the offending file in the filesystem before the application is started. Therefore, Id say the risk is fairly low. |
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.