chore(findings): opensource/k8ssandra/cass-management-api
Summary
opensource/k8ssandra/cass-management-api has 6 new findings discovered during continuous monitoring.
More information can be found in the VAT located here: https://vat.dso.mil/vat/image?imageName=opensource/k8ssandra/cass-management-api&tag=5.0.4&branch=master
EPSS (Exploit Prediction Scoring System) provides an estimate of the likelihood that a vulnerability will be exploited in the wild.
KEV (Known Exploited Vulnerabilities) indicates whether a vulnerability is actively being exploited according to CISA.
| id | source | severity | package | impact | workaround | epss_score | kev |
|---|---|---|---|---|---|---|---|
| b38400e99f6ca917736a076d58aaf98a | Anchore Compliance | Low | N/A | N/A | |||
| a98cf0855d75559fa066ce482f188a61 | Anchore Compliance | Low | N/A | N/A | |||
| 84a8237ac2baee277a05a73dd2baecab | Anchore Compliance | Low | N/A | N/A | |||
| 59e97d78f5482b9bbc0c5f30118f4b1b | Anchore Compliance | Low | N/A | N/A | |||
| 54bc816e0bc5e1545b1896b69c612962 | Anchore Compliance | Low | N/A | N/A | |||
| 025d7a1436e250cb601e0b2428d790f4 | Anchore Compliance | Low | N/A | N/A |
More information can be found in the VAT located here: https://vat.dso.mil/vat/image?imageName=opensource/k8ssandra/cass-management-api&tag=5.0.4&branch=master
Novel Tidelift Findings (Experimental)
opensource/k8ssandra/cass-management-api has 75 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 | epss_score | kev |
|---|---|---|---|---|---|---|
| CVE-2022-1471 | 9.8 | org.yaml:snakeyaml-1.26 | 0.93849 | N/A | ||
| CVE-2022-1471 | 9.8 | org.yaml:snakeyaml-1.32 | 0.93849 | N/A | ||
| CVE-2016-5699 | 6.1 | urllib3-1.24.2 | Its unlikely for an attacker to control URLs. | Reject URLs with rn or encode those characters. | 0.10221 | false |
| CVE-2019-9740 | 6.1 | urllib3-1.24.2 | Its unlikely for an attacker to control the URL youre fetching. | 0.06376 | N/A | |
| CVE-2023-32681 | 6.1 | requests-2.20.0 | Requires that deployment or integration of requests is being used to a connect to untrusted hosts b is connecting over HTTPS and c is using proxies to do so. | 0.04731 | false | |
| CVE-2019-11324 | 7.5 | urllib3-1.24.2 | cacerts is a commonly used parameter. | 0.01379 | N/A | |
| CVE-2024-47561 | 9.8 | org.apache.avro:avro-1.10.2 | 0.01066 | false | ||
| CVE-2021-33503 | 7.5 | urllib3-1.24.2 | Attackers dont usually control the URLs that urllib3 fetches. | Its possible but inconvenient to filter URLs with many . | 0.00863 | N/A |
| CVE-2018-8088 | 9.8 | org.slf4j:slf4j-api-1.7.25 | As far as we know, the vulberable constructor org.slf4j.ext.EventData class is called by org.apache.logging.log4jlog4jslf4jimpl log4j 2 module by the org.apache.logging.slf4j.EventDataConverter class. This class does not seem to be in wide use. | 0.00836 | N/A | |
| CVE-2019-11236 | 6.1 | urllib3-1.24.2 | Its unlikely for an attacker to control an URL. | Reject queries with rn or encode those characters. | 0.00636 | N/A |
| CVE-2021-43045 | 7.5 | org.apache.avro:avro-1.10.2 | 0.00613 | N/A | ||
| CVE-2023-43804 | 8.1 | urllib3-1.24.2 | Usage of the Cookie header is rare with urllib3. This is more common and useful in browsers. Redirections to another origin are also not the common case. | 0.00554 | false | |
| CVE-2022-38749 | 6.5 | org.yaml:snakeyaml-1.26 | 0.00543 | N/A | ||
| CVE-2024-26308 | 5.5 | org.apache.commons:commons-compress-1.21 | If you unpack a file in the Pack200 format, and that file has been specially crafted or corrupted, the library will attempt to allocate more memory than is available. | 0.00442 | false | |
| CVE-2023-34462 | 6.5 | io.netty:netty-handler-4.1.86.Final | Its relatively easy to trigger DoS and make the server suffer from unnecessarily high memory usage by leveraging this vulnerability. | You can fork the fixed SniHandler in newer Netty version instead of using the one provided by the old Netty version. Alternatively, you can simply disable SNI by removing SniHandler from your channel pipeline. | 0.00416 | false |
| CVE-2019-9947 | 6.1 | urllib3-1.24.2 | Its unlikely for an attacker to control an URL. | Reject URLs with rn or encode those characters. | 0.00402 | N/A |
| CVE-2023-6378 | 7.5 | ch.qos.logback:logback-classic-1.2.9 | Assuming logbackreceiver is not reachable outside the network of the user, only malevolent users inside the local network may mount a successful attack. | Do not enable the logbackreceiver component. | 0.00385 | false |
| CVE-2023-6378 | 7.5 | ch.qos.logback:logback-core-1.2.12 | Assuming logbackreceiver is not reachable outside the network of the user, only malevolent users inside the local network may mount a successful attack. | Do not enable the logbackreceiver component. | 0.00385 | false |
| CVE-2023-6378 | 7.5 | ch.qos.logback:logback-classic-1.2.12 | Assuming logbackreceiver is not reachable outside the network of the user, only malevolent users inside the local network may mount a successful attack. | Do not enable the logbackreceiver component. | 0.00385 | false |
| CVE-2023-6378 | 7.5 | ch.qos.logback:logback-core-1.2.9 | Assuming logbackreceiver is not reachable outside the network of the user, only malevolent users inside the local network may mount a successful attack. | Do not enable the logbackreceiver component. | 0.00385 | false |
| CVE-2022-40897 | 7.5 | setuptools-50.3.2 | Code path is deprecated. | 0.00318 | N/A | |
| CVE-2022-40897 | 7.5 | setuptools-39.2.0 | Code path is deprecated. | 0.00318 | N/A | |
| CVE-2023-6481 | 7.5 | ch.qos.logback:logback-classic-1.2.9 | Assuming logbackreceiver is not reachable outside the network of the user, only malevolent users inside the local network may mount a successful attack. | Assuming new softwarew deployment is possible, then there is no reason not to upgrade as 1.2.x, 1.3.x and 1.4.x series all have patched versions containing the appropriate fix. However, if new deploment is impossible, then disabling the logbackreceiver will prevent a successful attack. | 0.00312 | false |
| CVE-2023-6481 | 7.5 | ch.qos.logback:logback-core-1.2.12 | Assuming logbackreceiver is not reachable outside the network of the user, only malevolent users inside the local network may mount a successful attack. | Assuming new softwarew deployment is possible, then there is no reason not to upgrade as 1.2.x, 1.3.x and 1.4.x series all have patched versions containing the appropriate fix. However, if new deploment is impossible, then disabling the logbackreceiver will prevent a successful attack. | 0.00312 | false |
| CVE-2023-6481 | 7.5 | ch.qos.logback:logback-classic-1.2.12 | Assuming logbackreceiver is not reachable outside the network of the user, only malevolent users inside the local network may mount a successful attack. | Assuming new softwarew deployment is possible, then there is no reason not to upgrade as 1.2.x, 1.3.x and 1.4.x series all have patched versions containing the appropriate fix. However, if new deploment is impossible, then disabling the logbackreceiver will prevent a successful attack. | 0.00312 | false |
| CVE-2023-6481 | 7.5 | ch.qos.logback:logback-core-1.2.9 | Assuming logbackreceiver is not reachable outside the network of the user, only malevolent users inside the local network may mount a successful attack. | Assuming new softwarew deployment is possible, then there is no reason not to upgrade as 1.2.x, 1.3.x and 1.4.x series all have patched versions containing the appropriate fix. However, if new deploment is impossible, then disabling the logbackreceiver will prevent a successful attack. | 0.00312 | false |
| CVE-2023-33201 | 5.3 | org.bouncycastle:bcpkix-jdk15on-1.69 | 0.00282 | false | ||
| CVE-2023-33201 | 5.3 | org.bouncycastle:bcprov-jdk15on-1.69 | 0.00282 | false | ||
| CVE-2023-33201 | 5.3 | org.bouncycastle:bcprov-ext-jdk15on-1.69 | 0.00282 | false | ||
| CVE-2022-25857 | 7.5 | org.yaml:snakeyaml-1.26 | 0.00280 | N/A | ||
| CVE-2021-3572 | 5.7 | pip-20.2.4 | 0.00240 | N/A | ||
| CVE-2024-6345 | 8.8 | setuptools-50.3.2 | Most users have migrated off of the code paths that are affected. The affected code paths are actively deprecated and planned for turn down. Only specialized and legacy workflows are affected. | Use recommended installers pip, uv, build, system package managers to install all packages from trusted indexes. If working with untrusted content in private indexes, consider scanning for malicious code in the package index pages. | 0.00227 | false |
| CVE-2024-6345 | 8.8 | setuptools-39.2.0 | Most users have migrated off of the code paths that are affected. The affected code paths are actively deprecated and planned for turn down. Only specialized and legacy workflows are affected. | Use recommended installers pip, uv, build, system package managers to install all packages from trusted indexes. If working with untrusted content in private indexes, consider scanning for malicious code in the package index pages. | 0.00227 | false |
| CVE-2020-26137 | 6.5 | urllib3-1.24.2 | Its unlikely to use putrequest which is not documented as part of urllib3s API, but only inherited from http.client. | 0.00215 | N/A | |
| CVE-2024-30172 | 7.5 | org.bouncycastle:bcprov-jdk15on-1.69 | 0.00187 | false | ||
| CVE-2022-42004 | 7.5 | com.fasterxml.jackson.core:jackson-databind-2.13.2.2 | Attacker will need to have high confidence that the feature is enabled and be familiar with the object structure of the Java class target it is not possible to generate general JSON document since target type varies by system. | 0.00180 | N/A | |
| CVE-2022-42003 | 7.5 | com.fasterxml.jackson.core:jackson-databind-2.13.2.2 | Attacker will need to have high confidence that the feature is enabled and be familiar with the object structure of the Java class target it is not possible to generate general JSON document since target type varies by system. | 0.00168 | N/A | |
| CVE-2022-38752 | 6.5 | org.yaml:snakeyaml-1.26 | 0.00167 | N/A | ||
| CVE-2022-38751 | 6.5 | org.yaml:snakeyaml-1.26 | 0.00163 | N/A | ||
| CVE-2024-12798 | 5.9 | ch.qos.logback:logback-core-1.2.12 | The vulnerability assumes that the attacker has the ability to modify configuration files or alternatively has the ability modify environment variables used in the targeted applications launch script. This requires a high level of existing privilege. | The attack is exploitable only if the Janino library is available on the class path of the application. If Janino is not on the classpath, then the vulnerability is not possible. | 0.00150 | false |
| CVE-2024-12798 | 5.9 | ch.qos.logback:logback-core-1.2.9 | The vulnerability assumes that the attacker has the ability to modify configuration files or alternatively has the ability modify environment variables used in the targeted applications launch script. This requires a high level of existing privilege. | The attack is exploitable only if the Janino library is available on the class path of the application. If Janino is not on the classpath, then the vulnerability is not possible. | 0.00150 | false |
| CVE-2024-29857 | 7.5 | org.bouncycastle:bcprov-jdk15on-1.69 | 0.00148 | false | ||
| CVE-2024-53990 | 9.2 | org.asynchttpclient:async-http-client-2.12.1 | 0.00112 | false | ||
| CVE-2025-24970 | 7.5 | io.netty:netty-handler-4.1.96.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, .... | 0.00090 | false |
| CVE-2025-24970 | 7.5 | io.netty:netty-handler-4.1.112.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, .... | 0.00090 | false |
| CVE-2022-38750 | 5.5 | org.yaml:snakeyaml-1.26 | 0.00080 | N/A | ||
| CVE-2022-41854 | 6.5 | org.yaml:snakeyaml-1.26 | 0.00076 | N/A | ||
| CVE-2022-41854 | 6.5 | org.yaml:snakeyaml-1.32 | 0.00076 | N/A | ||
| CVE-2023-45803 | 4.2 | urllib3-1.24.2 | No exploits from real world were reported | Disable redirects for services that you arent expecting to respond with redirects with redirectsFalse.Disable automatic redirects with redirectsFalse and handle 303 redirects manually by stripping the HTTP request body. | 0.00062 | false |
| CVE-2023-33202 | 5.5 | org.bouncycastle:bcprov-jdk15on-1.69 | 0.00059 | false | ||
| CVE-2023-33202 | 5.5 | org.bouncycastle:bcprov-ext-jdk15on-1.69 | 0.00059 | false | ||
| CVE-2024-29025 | 5.3 | io.netty:netty-codec-http-4.1.86.Final | HttpPostRequestDecoder is vulnerable to this issue regardless of whether it is used as intended or not. | If HttpPostRequestDecoder is NOT used for handling file uploads, a user could limit the length of an HTTP POST request body to a small value, which will effectively reduce the theoretically possible maximum number of form fields a request body can contain. However, this workaround might not be feasible if a user needs to handle file uploads, which may not be possible to limit the request both length. | 0.00056 | false |
| CVE-2024-29025 | 5.3 | io.netty:netty-codec-http-4.1.96.Final | HttpPostRequestDecoder is vulnerable to this issue regardless of whether it is used as intended or not. | If HttpPostRequestDecoder is NOT used for handling file uploads, a user could limit the length of an HTTP POST request body to a small value, which will effectively reduce the theoretically possible maximum number of form fields a request body can contain. However, this workaround might not be feasible if a user needs to handle file uploads, which may not be possible to limit the request both length. | 0.00056 | false |
| CVE-2024-9622 | 5.3 | org.jboss.resteasy:resteasy-netty4-6.2.10.Final | 0.00054 | false | ||
| CVE-2024-30171 | 5.9 | org.bouncycastle:bcprov-jdk15on-1.69 | 0.00050 | false | ||
| CVE-2023-39410 | 7.5 | org.apache.avro:avro-1.10.2 | 0.00045 | false | ||
| CVE-2025-46392 | 2.7 | commons-configuration:commons-configuration-1.10 | 0.00042 | false | ||
| CVE-2023-2976 | 7.1 | com.google.guava:guava-30.1.1-jre | 0.00041 | false | ||
| CVE-2023-2976 | 7.1 | com.google.guava:guava-31.0.1-jre | 0.00041 | false | ||
| CVE-2024-47535 | 5.5 | io.netty:netty-common-4.1.112.Final | An attacker must acquire the privilege to override the content of system files such as etcresolv.conf and procsys. Given such powerful superuserlevel privilege, I would imagine the attacker will not waste their time to trigger OOME using this vulnerability. | 0.00039 | false | |
| CVE-2024-47535 | 5.5 | io.netty:netty-common-4.1.86.Final | An attacker must acquire the privilege to override the content of system files such as etcresolv.conf and procsys. Given such powerful superuserlevel privilege, I would imagine the attacker will not waste their time to trigger OOME using this vulnerability. | 0.00039 | false | |
| CVE-2024-47535 | 5.5 | io.netty:netty-common-4.1.96.Final | An attacker must acquire the privilege to override the content of system files such as etcresolv.conf and procsys. Given such powerful superuserlevel privilege, I would imagine the attacker will not waste their time to trigger OOME using this vulnerability. | 0.00039 | false | |
| CVE-2024-12801 | 2.4 | ch.qos.logback:logback-core-1.2.12 | A successful attack requires that the attacker has write access to the logback.xml configuration file in use. | 0.00039 | false | |
| CVE-2024-12801 | 2.4 | ch.qos.logback:logback-core-1.2.9 | A successful attack requires that the attacker has write access to the logback.xml configuration file in use. | 0.00039 | false | |
| CVE-2025-25193 | 5.5 | io.netty:netty-common-4.1.112.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. | 0.00035 | false | |
| CVE-2025-25193 | 5.5 | io.netty:netty-common-4.1.86.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. | 0.00035 | false | |
| CVE-2025-25193 | 5.5 | io.netty:netty-common-4.1.96.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. | 0.00035 | false | |
| CVE-2024-47554 | 4.3 | commons-io:commons-io-2.8.0 | Either an application is using the class org.apache.commons.io.input.XmlStreamReader or it is not if the class is in use then attackers can craft malicious input to make the application vulnerable if that application accepts input to XmlStreamReader from the world at large. If an application can be relatively certain that its XmlStreamReader input can be trusted, the risk could be lowered from a vulnerability to a bug. | An application could mitigate this vulnerability by validating the input given to the class. | 0.00035 | false |
| CVE-2024-37891 | 4.4 | urllib3-1.24.2 | Theres no reason to set ProxyAuthorization without using urllib3s proxy support. | Using the ProxyAuthorization header with urllib3s ProxyManager. Disabling HTTP redirects using redirectsFalse when sending requests. Not using the ProxyAuthorization header. | 0.00033 | false |
| CVE-2023-35116 | 4.7 | com.fasterxml.jackson.core:jackson-databind-2.13.2.2 | 0.00015 | false | ||
| CVE-2023-35116 | 4.7 | com.fasterxml.jackson.core:jackson-databind-2.13.4.2 | 0.00015 | false | ||
| CVE-2023-35116 | 4.7 | com.fasterxml.jackson.core:jackson-databind-2.15.2 | 0.00015 | false | ||
| CVE-2024-25710 | 5.5 | org.apache.commons:commons-compress-1.21 | If you read a DUMP file that is specially crafted or corrupted, the library will enter an infinite loop. | 0.00012 | false | |
| CVE-2020-8908 | 3.3 | com.google.guava:guava-30.1.1-jre | 0.00008 | N/A | ||
| CVE-2020-8908 | 3.3 | com.google.guava:guava-31.0.1-jre | 0.00008 | N/A |
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.