Vulnerability Monitor

The vendors, products, and vulnerabilities you care about

perforce

About This Vendor

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

Vulnerability Trends for This Vendor

SecUtils has indexed 26 known vulnerabilities from perforce. This includes 2 critical-severity issues and 8 high-severity issues that represent significant risk. These vulnerabilities affect 13 distinct products across perforce's portfolio, demonstrating the breadth of the vendor's product ecosystem and the importance of comprehensive patch management strategies. Disclosure dates span from 2007 through 2025, indicating decades of continuous security attention and research. Organizations deploying perforce 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-0100 2007-01-08 2026-06-16 - 10.0 Likely
CVE-2007-6349 2007-12-20 2026-06-16 - 7.8 Likely
CVE-2008-1302 2008-03-12 2026-06-16 - 5.0 Likely
CVE-2008-1303 2008-03-12 2026-06-16 - 5.0 Likely
CVE-2008-1338 2008-03-14 2026-06-16 - 7.8 Likely
CVE-2010-0929 2010-03-05 2026-06-16 - 5.0 Likely
CVE-2010-0930 2010-03-05 2026-06-16 - 5.0 Likely
CVE-2010-0931 2010-03-05 2026-06-16 - 5.0 Likely
CVE-2010-0932 2010-03-05 2026-06-16 - 5.0 Likely
CVE-2010-0933 2010-03-05 2026-06-16 - 6.8 Likely
CVE-2010-0934 2010-03-05 2026-06-16 - 7.1 Unknown
CVE-2010-0935 2010-03-05 2026-06-16 - 4.6 Unknown
CVE-2015-8965 2017-04-06 2026-06-17 9.8 7.5 Likely
CVE-2018-1000147 2018-04-05 2026-06-17 6.5 4.0 Likely
CVE-2013-1410 2020-02-12 2026-06-16 6.1 4.3 Likely
CVE-2021-28973 2021-04-13 2026-06-17 4.9 4.0 Likely
CVE-2022-2394 2022-07-19 2026-06-17 4.1 - -
CVE-2023-35767 2023-11-08 2026-06-17 7.5 - -
CVE-2023-45319 2023-11-08 2026-06-17 7.5 - -
CVE-2023-45849 2023-11-08 2026-06-17 9.0 - -
CVE-2023-5759 2023-11-08 2026-06-17 7.5 - -
CVE-2024-0325 2024-02-01 2026-06-17 3.6 - -
CVE-2024-3930 2024-07-30 2026-06-17 6.3 - -
CVE-2024-5249 2024-07-30 2026-06-17 5.4 - -
CVE-2024-5250 2024-07-30 2026-06-17 3.5 - -
CVE-2025-14591 2025-12-20 2026-06-17 7.5 - -

How SecUtils Normalizes Vendor Data

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