Vulnerability Monitor

The vendors, products, and vulnerabilities you care about

icu-project

About This Vendor

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

Vulnerability Trends for This Vendor

SecUtils has indexed 21 known vulnerabilities from icu-project. This includes 7 critical-severity issues and 11 high-severity issues that represent significant risk. These vulnerabilities affect 21 distinct products across icu-project's portfolio, demonstrating the breadth of the vendor's product ecosystem and the importance of comprehensive patch management strategies. Disclosure dates span from 2008 through 2020, indicating decades of continuous security attention and research. Organizations deploying icu-project 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-2007-4770 2008-01-29 2025-04-09 - 6.8 Likely
CVE-2007-4771 2008-01-29 2025-04-09 - 9.3 Likely
CVE-2011-4599 2012-06-21 2025-04-11 - 7.5 Likely
CVE-2014-7923 2015-01-22 2025-04-12 - 7.5 Likely
CVE-2014-7926 2015-01-22 2025-04-12 - 7.5 Likely
CVE-2014-7940 2015-01-22 2025-04-12 - 7.5 Likely
CVE-2014-8146 2015-05-25 2025-04-12 - 7.5 Likely
CVE-2014-8147 2015-05-25 2025-04-12 - 7.5 Likely
CVE-2015-5922 2015-10-09 2025-04-12 - 10.0 Likely
CVE-2016-6293 2016-07-25 2025-04-12 9.8 7.5 Likely
CVE-2016-7415 2016-09-17 2025-04-12 9.8 7.5 Likely
CVE-2014-9911 2017-01-04 2025-04-12 9.8 7.5 Likely
CVE-2017-7867 2017-04-14 2025-04-20 7.5 5.0 Likely
CVE-2017-7868 2017-04-14 2025-04-20 7.5 5.0 Likely
CVE-2014-9654 2017-04-24 2025-04-20 9.8 7.5 Likely
CVE-2017-14952 2017-10-16 2025-04-20 9.8 7.5 Likely
CVE-2017-17484 2017-12-10 2025-04-20 9.8 7.5 Likely
CVE-2017-15422 2018-08-28 2024-11-21 6.5 4.3 Likely
CVE-2017-15396 2018-08-28 2024-11-21 6.5 4.3 Likely
CVE-2018-18928 2018-11-04 2024-11-21 9.8 7.5 Likely
CVE-2020-10531 2020-03-12 2024-11-21 8.8 6.8 Likely

How SecUtils Normalizes Vendor Data

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