Vulnerability Monitor

The vendors, products, and vulnerabilities you care about

midnight_commander

About This Vendor

midnight_commander is a technology vendor producing software and infrastructure products. As a software provider, midnight_commander's broad product portfolio across multiple domains—including operating systems, cloud infrastructure, enterprise applications, databases, networking, and security tools—creates a large attack surface. Additionally, long support cycles, widespread deployment, and continuous feature development contribute to the accumulation of discovered vulnerabilities over time. Major vendors typically report higher CVE counts not necessarily due to inferior security, but because of greater exposure to security research, responsible disclosure practices, and the sheer complexity of maintaining multiple product lines and legacy systems. Regular security assessments and patching of midnight_commander's products are critical for organizations running their software in production environments.

Vulnerability Trends for This Vendor

SecUtils has indexed 20 known vulnerabilities from midnight_commander. This includes 6 high-severity issues requiring prompt remediation. These vulnerabilities affect 10 distinct products across midnight_commander's portfolio, demonstrating the breadth of the vendor's product ecosystem and the importance of comprehensive patch management strategies. Disclosure dates span from 1999 through 2005, reflecting sustained security scrutiny over multiple years. Organizations deploying midnight_commander products should maintain active vulnerability monitoring, prioritize critical patches, and implement compensating controls where patches cannot be applied immediately.

ID Date Published Last Modified Severity (CVSSv3) Severity (CVSSv2) Exploit Available
CVE-1999-0480 1999-04-01 2025-04-03 - 2.1 Unknown
CVE-1999-1337 1999-08-01 2025-04-03 - 4.6 Unknown
CVE-2000-1108 2001-01-09 2025-04-03 - 4.6 Unknown
CVE-2000-1109 2001-01-09 2025-04-03 - 4.6 Unknown
CVE-2001-1429 2001-11-12 2025-04-03 - 4.6 Unknown
CVE-2003-1023 2004-01-20 2025-04-03 - 7.5 Likely
CVE-2004-0226 2004-08-18 2025-04-03 - 10.0 Likely
CVE-2004-0231 2004-08-18 2025-04-03 - 2.1 Unknown
CVE-2004-0232 2004-08-18 2025-04-03 - 5.0 Likely
CVE-2004-1004 2005-04-14 2025-04-03 - 7.5 Likely
CVE-2004-1005 2005-04-14 2025-04-03 - 7.5 Likely
CVE-2004-1009 2005-04-14 2025-04-03 - 5.0 Likely
CVE-2004-1090 2005-04-14 2025-04-03 - 5.0 Likely
CVE-2004-1091 2005-04-14 2025-04-03 - 5.0 Likely
CVE-2004-1092 2005-04-14 2025-04-03 - 5.0 Likely
CVE-2004-1093 2005-04-14 2025-04-03 - 5.0 Likely
CVE-2004-1174 2005-04-14 2025-04-03 - 5.0 Likely
CVE-2004-1175 2005-04-14 2025-04-03 - 7.5 Likely
CVE-2004-1176 2005-04-14 2025-04-03 - 7.5 Likely
CVE-2005-0763 2005-05-02 2025-04-03 - 4.6 Unknown

How SecUtils Normalizes Vendor Data

SecUtils aggregates National Vulnerability Database (NVD) and MITRE records for midnight_commander by normalizing vendor identifiers across diverse data sources, mapping vendor names to their associated product lines, and collecting all known vulnerabilities under a unified vendor context. For every CVE associated with midnight_commander's products, we extract and structure Common Platform Enumeration (CPE) data, Common Weakness Enumeration (CWE) categories, CVSS severity metrics, and reference links to enable rapid vulnerability identification and asset correlation. This record contains no exploit code, proof-of-concept instructions, or attack methodologies—only defensive intelligence necessary for patch management, risk assessment, and vendor vulnerability tracking.