Vulnerability Monitor

The vendors, products, and vulnerabilities you care about

jelsoft

About This Vendor

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

Vulnerability Trends for This Vendor

SecUtils has indexed 60 known vulnerabilities from jelsoft. This includes 18 high-severity issues requiring prompt remediation. These vulnerabilities affect 8 distinct products across jelsoft's portfolio, demonstrating the breadth of the vendor's product ecosystem and the importance of comprehensive patch management strategies. Disclosure dates span from 2001 through 2009, reflecting sustained security scrutiny over multiple years. Organizations deploying jelsoft 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-2001-0475 2001-06-27 2025-04-03 - 7.5 Likely
CVE-2002-1660 2002-12-31 2025-04-03 - 7.5 Likely
CVE-2002-1678 2002-12-31 2025-04-03 - 4.3 Likely
CVE-2002-1679 2002-12-31 2025-04-03 - 4.3 Likely
CVE-2002-1922 2002-12-31 2025-04-03 - 4.3 Likely
CVE-2002-2235 2002-12-31 2025-04-03 - 5.0 Likely
CVE-2003-0295 2003-06-16 2025-04-03 - 6.8 Likely
CVE-2004-0036 2004-01-20 2025-04-03 - 5.0 Likely
CVE-2003-1031 2004-02-17 2025-04-03 - 4.3 Likely
CVE-2004-0091 2004-02-17 2025-04-03 - 4.3 Likely
CVE-2004-0620 2004-12-06 2025-04-03 - 4.3 Likely
CVE-2004-1515 2004-12-31 2025-04-03 - 7.5 Likely
CVE-2004-1823 2004-12-31 2025-04-03 - 4.3 Likely
CVE-2004-1824 2004-12-31 2025-04-03 - 4.3 Likely
CVE-2004-2076 2004-12-31 2025-04-03 - 4.3 Likely
CVE-2004-2288 2004-12-31 2025-04-03 - 4.3 Likely
CVE-2004-2695 2004-12-31 2025-04-03 - 7.5 Likely
CVE-2005-0511 2005-02-21 2025-04-03 - 7.5 Likely
CVE-2005-0429 2005-05-02 2025-04-03 - 5.0 Likely
CVE-2005-3019 2005-09-21 2025-04-03 - 7.5 Likely
CVE-2005-3020 2005-09-21 2025-04-03 - 4.3 Likely
CVE-2005-3021 2005-09-21 2025-04-03 - 2.1 Unknown
CVE-2005-3022 2005-09-21 2025-04-03 - 7.5 Likely
CVE-2005-3023 2005-09-21 2025-04-03 - 4.3 Likely
CVE-2005-3024 2005-09-21 2025-04-03 - 7.5 Likely
CVE-2005-3025 2005-09-21 2025-04-03 - 4.3 Likely
CVE-2005-4621 2005-12-31 2025-04-03 - 4.3 Likely
CVE-2006-0080 2006-01-04 2025-04-03 - 4.3 Likely
CVE-2006-1040 2006-03-07 2025-04-03 - 4.3 Likely
CVE-2006-1382 2006-03-24 2025-04-03 - 7.5 Likely
CVE-2006-1673 2006-04-07 2025-04-03 - 2.6 Unknown
CVE-2006-1816 2006-04-18 2025-04-03 - 5.0 Likely
CVE-2006-2018 2006-04-25 2025-04-03 - 7.5 Likely
CVE-2006-2335 2006-05-12 2025-04-03 - 6.5 Likely
CVE-2006-2805 2006-06-03 2025-04-03 - 5.0 Likely
CVE-2006-3253 2006-06-28 2025-04-03 - 2.6 Unknown
CVE-2006-4271 2006-08-21 2025-04-03 - 7.5 Likely
CVE-2006-4272 2006-08-21 2025-04-03 - 7.5 Likely
CVE-2006-4273 2006-08-21 2025-04-03 - 6.8 Likely
CVE-2006-5104 2006-10-03 2025-04-09 - 7.5 Likely
CVE-2006-6040 2006-11-22 2025-04-09 - 6.8 Likely
CVE-2006-6779 2006-12-28 2025-04-09 - 6.8 Likely
CVE-2007-0830 2007-02-07 2025-04-09 - 3.5 Unknown
CVE-2007-0869 2007-02-09 2025-04-09 - 4.3 Likely
CVE-2007-1292 2007-03-07 2025-04-09 - 7.5 Likely
CVE-2007-1342 2007-03-08 2025-04-09 - 4.3 Likely
CVE-2007-1573 2007-03-21 2025-04-09 - 6.0 Unknown
CVE-2007-2908 2007-05-30 2025-04-09 - 4.3 Likely
CVE-2007-2909 2007-05-30 2025-04-09 - 3.5 Unknown
CVE-2007-2910 2007-05-30 2025-04-09 - 4.3 Likely
CVE-2007-2911 2007-05-30 2025-04-09 - 8.5 Unknown
CVE-2007-2912 2007-05-30 2025-04-09 - 5.0 Likely
CVE-2007-3196 2007-06-12 2025-04-09 - 7.5 Likely
CVE-2007-3197 2007-06-12 2025-04-09 - 7.5 Likely
CVE-2007-3326 2007-06-21 2025-04-09 - 5.8 Likely
CVE-2007-4120 2007-08-01 2025-04-09 - 9.3 Likely
CVE-2007-4453 2007-08-21 2025-04-09 - 4.3 Likely
CVE-2007-4959 2007-09-18 2025-04-09 - 4.3 Likely
CVE-2008-6754 2009-04-27 2025-04-09 - 4.0 Likely
CVE-2009-2172 2009-06-23 2025-04-09 - 4.3 Likely

How SecUtils Normalizes Vendor Data

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