Vulnerability Monitor

The vendors, products, and vulnerabilities you care about

mirabilis

About This Vendor

mirabilis is a technology vendor producing software and infrastructure products. As a software provider, mirabilis'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 mirabilis's products are critical for organizations running their software in production environments.

Vulnerability Trends for This Vendor

SecUtils has indexed 27 known vulnerabilities from mirabilis. This includes 9 high-severity issues requiring prompt remediation. These vulnerabilities affect 5 distinct products across mirabilis's portfolio, demonstrating the breadth of the vendor's product ecosystem and the importance of comprehensive patch management strategies. Disclosure dates span from 1998 through 2006, reflecting sustained security scrutiny over multiple years. Organizations deploying mirabilis 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-1289 1998-11-11 2025-04-03 - 7.5 Likely
CVE-1999-1440 1999-01-01 2025-04-03 - 5.1 Unknown
CVE-1999-0474 1999-04-05 2025-04-03 - 5.0 Likely
CVE-1999-1418 1999-05-01 2025-04-03 - 5.0 Likely
CVE-2000-0046 2000-01-10 2025-04-03 - 7.5 Likely
CVE-2000-0564 2000-05-29 2025-04-03 - 5.0 Likely
CVE-2000-1078 2000-12-11 2025-04-03 - 5.0 Likely
CVE-2001-0367 2001-06-27 2025-04-03 - 5.0 Likely
CVE-2001-1305 2001-08-17 2025-04-03 - 5.0 Likely
CVE-2002-0028 2002-02-27 2025-04-03 - 7.5 Likely
CVE-2002-0254 2002-05-29 2025-04-03 - 5.0 Likely
CVE-2002-1743 2002-12-31 2025-04-03 - 5.0 Likely
CVE-2002-1773 2002-12-31 2025-04-03 - 7.5 Likely
CVE-2002-2075 2002-12-31 2025-04-03 - 5.0 Likely
CVE-2002-2329 2002-12-31 2025-04-03 - 7.8 Likely
CVE-2003-0235 2003-05-27 2025-04-03 - 7.5 Likely
CVE-2003-0236 2003-05-27 2025-04-03 - 7.5 Likely
CVE-2003-0237 2003-05-27 2025-04-03 - 7.5 Likely
CVE-2003-0238 2003-05-27 2025-04-03 - 5.0 Likely
CVE-2003-0239 2003-05-27 2025-04-03 - 5.0 Likely
CVE-2003-0769 2003-09-22 2025-04-03 - 4.3 Likely
CVE-2005-3433 2005-11-02 2025-04-03 - 5.1 Unknown
CVE-2006-0765 2006-02-18 2025-04-03 - 5.1 Unknown
CVE-2006-0766 2006-02-18 2025-04-03 - 5.1 Unknown
CVE-2006-2303 2006-05-11 2025-04-03 - 6.4 Likely
CVE-2006-4662 2006-09-09 2025-04-03 - 7.5 Likely
CVE-2006-5724 2006-11-04 2025-04-09 - 2.1 Unknown

How SecUtils Normalizes Vendor Data

SecUtils aggregates National Vulnerability Database (NVD) and MITRE records for mirabilis 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 mirabilis'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.