Does a CVE affect MetaDefender Storage Security?

In today's rapidly evolving digital landscape, understanding the impact of security vulnerabilities is more crucial than ever. The Common Vulnerabilities and Exposures (CVE) list is an invaluable resource for identifying potential security risks associated with software products. This article provides a comprehensive overview of various CVEs, helping you determine whether MetaDefender Storage Security is affected. By staying informed about these vulnerabilities, you can take proactive measures to protect your systems and data from potential threats.

CVE	Summary
CVE-2024-27322	MetaDefender Storage Security doesn't use R programming language within the product, we are not affected by CVE-2024-27322.
CVE-2024-4603	This vulnerability affects the functions `EVP_PKEY_param_check()` and `EVP_PKEY_public_check()`. Since these are not used, MetaDefender Storage Security is not affected.
CVE-2024-0727	Upon thorough review and analysis, it has been determined that all versions of the License SDK integrated with the MDSS product do not utilize any of the mentioned vulnerable functions. Hence, MetaDefender Storage Security is not affected by CVE-2024-0727.
CVE-2023-46589	MetaDefender Storage Security does not use Apache so it's not being affect by CVE-2023-46589
CVE-2023-44487	MetaDefender Storage Security is not impacted by CVE-2023-44487.
CVE-2024-41110	We tested with versions of Docker up to `Docker version 27.1.1`, build 6312585 and can confirm that MetaDefender Storage Security is not impacted by CVE-2024-41110
CVE-2024-7592	MetaDefender Storage Security is container based, and the python version used by MetaDefender Storage Security internally is 3.12, hence MetaDefender Storage Security is not impacted by CVE-2024-7592. Python libraries present on the host machine where MDSS is installed can be removed.
CVE-2018-15133	MetaDefender Storage Security does not use PHP and/or Laravel Framework so it's not affected

Support

If Further Assistance is required, please proceed to log a support case or chat with our support engineer.

Last updated on

Was this page helpful?