Vulnerability Monitor

The vendors, products, and vulnerabilities you care about

infoblox

About This Vendor

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

Vulnerability Trends for This Vendor

SecUtils has indexed 26 known vulnerabilities from infoblox. This includes 5 critical-severity issues and 11 high-severity issues that represent significant risk. These vulnerabilities affect 16 distinct products across infoblox's portfolio, demonstrating the breadth of the vendor's product ecosystem and the importance of comprehensive patch management strategies. Disclosure dates span from 2002 through 2026, indicating decades of continuous security attention and research. Organizations deploying infoblox 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-2002-2213 2002-12-31 2025-04-03 - 5.0 Likely
CVE-2004-0460 2004-08-06 2025-04-03 - 10.0 Likely
CVE-2004-0461 2004-08-06 2025-04-03 - 10.0 Likely
CVE-2004-0606 2004-12-06 2025-04-03 - 6.8 Likely
CVE-2011-5178 2012-09-20 2025-04-11 - 4.3 Likely
CVE-2014-3418 2014-07-15 2025-04-12 - 10.0 Likely
CVE-2014-3419 2014-07-15 2025-04-12 - 7.2 Unknown
CVE-2015-2033 2015-02-20 2025-04-12 - 10.0 Likely
CVE-2016-6484 2017-01-23 2025-04-20 6.1 4.3 Likely
CVE-2018-6643 2018-08-28 2024-11-21 6.1 4.3 Likely
CVE-2018-10239 2019-06-17 2024-11-21 6.7 7.2 Unknown
CVE-2020-15303 2021-06-28 2024-11-21 6.5 4.0 Likely
CVE-2022-32972 2023-02-17 2025-03-18 7.8 - -
CVE-2023-37249 2023-08-25 2024-11-21 8.8 - -
CVE-2022-28975 2024-01-09 2026-01-27 5.4 - -
CVE-2024-36046 2025-02-27 2025-04-10 9.8 - -
CVE-2024-36047 2025-02-27 2025-04-10 9.8 - -
CVE-2024-37566 2025-02-27 2025-04-10 9.8 - -
CVE-2024-37567 2025-02-27 2025-04-10 9.1 - -
CVE-2024-54188 2025-05-22 2025-06-03 5.3 - -
CVE-2025-32813 2025-05-22 2025-06-03 7.2 - -
CVE-2025-32814 2025-05-22 2025-06-03 9.8 - -
CVE-2025-32815 2025-05-22 2025-06-03 6.5 - -
CVE-2024-52874 2025-05-22 2025-05-30 8.8 - -
CVE-2025-61879 2026-02-12 2026-02-19 7.7 - -
CVE-2025-61880 2026-02-12 2026-02-19 8.8 - -

How SecUtils Normalizes Vendor Data

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