Security readout for executives and security teams
This is an old Yahoo Messenger buffer overflow. A remote attacker could send an oversized buddy-group value that may crash the client and could possibly run code. Business urgency is low unless legacy Yahoo Messenger from before February 2002 still exists in the environment. Exposure is likely limited to legacy systems running Yahoo Messenger versions from before February 2002. Modern environments should have no exposure unless old endpoint images, lab systems, archived virtual machines, or unmanaged desktops still retain the vulnerable client. Prioritize only if legacy Yahoo Messenger is still present. The main business risk is unmanaged old software on endpoints, not a current widespread internet-facing service exposure. Mitigation focus: Identify and remove Yahoo Messenger versions from before February 2002.; Upgrade any required legacy client using vendor or CERT guidance.; Block or retire unsupported instant messaging clients on managed endpoints..
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
Execution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2002-1665 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.