Security readout for executives and security teams
This is an old Yahoo Messenger issue where specially crafted ymsgr links could overflow memory and potentially run attacker-controlled code. The business risk is mainly legacy exposure: unsupported endpoints still running Yahoo Messenger 5.0.0.1064 or earlier. Exposure is likely limited to legacy systems with Yahoo Messenger 5.0.0.1064 or earlier installed and ymsgr URI handling registered. Modern environments are unlikely to be affected unless old software remains on endpoints. Prioritize remediation if any vulnerable Yahoo Messenger installations are found. Otherwise, treat this as a legacy software eradication and asset-inventory control item, not a current emergency based on the supplied evidence. Mitigation focus: Identify and remove Yahoo Messenger 5.0.0.1064 or earlier from managed endpoints.; Check Yahoo, CERT, or vendor guidance for any available fixed version or workaround.; Disable or unregister ymsgr URI handling where legacy clients cannot be removed immediately..
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-0031 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.