Vulnerability Monitor

The vendors, products, and vulnerabilities you care about
messenger Vendor: yahoo

About This Product

messenger is a software product offered by yahoo. This product is widely deployed in production environments, making vulnerability monitoring essential for organizations relying on it. Security vulnerabilities in products of this category can affect system availability, data confidentiality, and integrity across entire networks. The moderate vulnerability count reflects ongoing security research and responsible disclosure practices. Regular assessment of known vulnerabilities and timely patching are fundamental components of responsible system administration for any deployment of this software.

Vulnerability Landscape Summary

SecUtils has identified 33 known vulnerabilities affecting yahoo messenger. This includes 14 high-severity issues requiring prompt remediation. Vulnerabilities in this product have been disclosed spanning from 2002 to 2015, indicating a sustained research interest and ongoing security attention. 16 medium-severity issues and 3 low-severity issues complete the vulnerability landscape. Organizations should prioritize patching based on deployment context, asset criticality, and exploitation likelihood rather than severity alone.

Known Vulnerabilities
ID Date Published Last Modified Severity (CVSSv3) Severity (CVSSv2) Exploit Available
CVE-2002-0320 2002-06-25 2025-04-03 - 7.5 Likely
CVE-2002-0321 2002-06-25 2025-04-03 - 5.0 Likely
CVE-2002-0322 2002-06-25 2025-04-03 - 7.5 Likely
CVE-2002-0031 2002-07-26 2025-04-03 - 4.6 Unknown
CVE-2002-0032 2002-07-26 2025-04-03 - 7.5 Likely
CVE-2002-1664 2002-12-31 2025-04-03 - 6.4 Likely
CVE-2002-1665 2002-12-31 2025-04-03 - 7.5 Likely
CVE-2002-2361 2002-12-31 2025-04-03 - 5.8 Likely
CVE-2003-1135 2003-12-31 2025-04-03 - 2.6 Unknown
CVE-2004-0043 2004-02-03 2025-04-03 - 7.5 Likely
CVE-2005-0243 2005-02-17 2025-04-03 - 5.0 Likely
CVE-2005-0242 2005-02-18 2025-04-03 - 4.6 Unknown
CVE-2005-0737 2005-05-02 2025-04-03 - 7.5 Likely
CVE-2005-1618 2005-05-16 2025-04-03 - 5.0 Likely
CVE-2005-1671 2005-05-19 2025-04-03 - 2.1 Unknown
CVE-2006-3298 2006-06-29 2025-04-03 - 5.0 Likely
CVE-2006-4975 2006-09-25 2025-04-03 - 2.6 Unknown
CVE-2006-5563 2006-10-27 2025-04-09 - 5.0 Likely
CVE-2006-6603 2006-12-15 2025-04-09 - 9.3 Likely
CVE-2007-0768 2007-02-06 2025-04-09 - 4.3 Likely
CVE-2007-0868 2007-02-09 2025-04-09 - 5.0 Likely
CVE-2007-1680 2007-04-06 2025-04-09 - 9.3 Likely
CVE-2007-3147 2007-06-11 2025-04-09 - 9.3 Likely
CVE-2007-3148 2007-06-11 2025-04-09 - 9.3 Likely
CVE-2007-3638 2007-07-10 2025-04-09 - 6.0 Unknown
CVE-2007-3928 2007-07-21 2025-04-09 - 7.6 Unknown
CVE-2007-4391 2007-08-17 2025-04-09 - 9.3 Likely
CVE-2007-4515 2007-08-31 2025-04-09 - 9.3 Likely
CVE-2007-4635 2007-08-31 2025-04-09 - 5.0 Likely
CVE-2007-5017 2007-09-20 2025-04-09 - 5.0 Likely
CVE-2009-4171 2009-12-02 2025-04-09 - 4.3 Likely
CVE-2012-0268 2012-01-19 2025-04-11 - 5.1 Unknown
CVE-2014-7216 2015-09-11 2025-04-12 - 9.3 Likely

How SecUtils Interprets Product Data

SecUtils normalizes and enriches National Vulnerability Database (NVD) records for yahoo messenger by standardizing vendor and product identifiers, aggregating vulnerability metadata from both NVD and MITRE sources, and structuring the data for rapid analysis and asset correlation. For every vulnerability listed, we extract Common Platform Enumeration (CPE) data, Common Weakness Enumeration (CWE) classifications, CVSS severity metrics, and reference information to enable organizations to prioritize patching and risk assessment efficiently. This record contains no exploit code, proof-of-concept instructions, or attack methodologies—only defensive intelligence necessary for vulnerability management and security operations.