Does a CVE affect MetaDefender MFT?

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 Managed File Transfer™ 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-2018-25103	MetaDefender Managed File Transfer™ does not utilize lighttpd in its architecture. Therefore, any vulnerabilities associated with lighttpd.
CVE-2024-40898	MetaDefender Managed File Transfer™ does not use Apache HTTP Server and is not affected by CVE-2024-40898
CVE-2024-4367	The related libraries for this CVE are not used in MetaDefender Managed File Transfer™, hence it's not affected
CVE-2024-34342	The related libraries for this CVE are not used in MetaDefender Managed File Transfer™, hence it's not affected
CVE-2024-4577	The related libraries for this CVE are not used in MetaDefender Managed File Transfer™, hence it's not affected
CVE-2019-9082	The related libraries for this CVE are not used in MetaDefender Managed File Transfer™, hence it's not affected
CVE-2020-17519	The related dependencies are not used in MetaDefender Managed File Transfer™, hence it's not affected
CVE-2024-4741	The related dependencies are not used in MetaDefender Managed File Transfer™, hence it's not affected
CVE-2024-38819	Spring framework is not used in MetaDefender Managed File Transfer™ hence it's not affected
CVE-2023-30547	The related dependencies are not used in MetaDefender Managed File Transfer™, hence 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?