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.

CVESummary
CVE-2018-25103MetaDefender Managed File Transfer™ does not utilize lighttpd in its architecture. Therefore, any vulnerabilities associated with lighttpd.
CVE-2024-40898MetaDefender Managed File Transfer™ does not use Apache HTTP Server and is not affected by CVE-2024-40898
CVE-2024-4367The related libraries for this CVE are not used in MetaDefender Managed File Transfer™, hence it's not affected
CVE-2024-34342The related libraries for this CVE are not used in MetaDefender Managed File Transfer™, hence it's not affected
CVE-2024-4577The related libraries for this CVE are not used in MetaDefender Managed File Transfer™, hence it's not affected
CVE-2019-9082The related libraries for this CVE are not used in MetaDefender Managed File Transfer™, hence it's not affected
CVE-2020-17519The related dependencies are not used in MetaDefender Managed File Transfer™, hence it's not affected
CVE-2024-4741The related dependencies are not used in MetaDefender Managed File Transfer™, hence it's not affected
CVE-2024-38819Spring framework is not used in MetaDefender Managed File Transfer™ hence it's not affected
CVE-2023-30547The related dependencies are not used in MetaDefender Managed File Transfer™, hence it's not affected
CVE-2024-10979MetaDefender Managed File Transfer™ does not use PostgresQL so it's not affected by CVE-2024-10979
CVE-2024-6387MetaDefender Managed File Transfer™ is not impacted by CVE-2024-6387
CVE-2021-44228MetaDefender Managed File Transfer™ use log4net, which is not affected by this vulnerability. This issue is specific to log4j-core and does not impact log4net, log4cxx, or other Apache Logging Services projects.
CVE-2018-15133MetaDefender Managed File Transfer™ does not use Laravel Framework, so it is not affected by this CVE
CVE-2024-3566MetaDefender Managed File Transfer™ is not affected by this CVE.
CVE-2024-27980MetaDefender Managed File Transfer™ is not affected by this CVE.
CVE-2024-1874MetaDefender Managed File Transfer™ is not affected by this CVE.
CVE-2024-24576MetaDefender Managed File Transfer™ is not affected by this CVE.
CVE-2024-40725This CVE is related to Apache HTTP Server which MetaDefender Managed File Transfer™ does not use so it's not affected
CVE-2024-27348This CVE is related to Apache HugeGraph-Server which MetaDefender Managed File Transfer™ does not use so it's not affected

If Further Assistance is required, please proceed to log a support case or chat with our support engineer.
Type to search, ESC to discard
Type to search, ESC to discard
Type to search, ESC to discard
Next to read:
How to troubleshoot MetaDefender Managed File Transfer becomes unreachable after enabling HTTPS?
On This Page
Does a CVE affect MetaDefender MFT?