| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.0 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical has been found in Yahoo! Messenger 5.5/5.6. This issue affects some unknown processing of the file ypager.exe of the component ysmgr URI Handler. This manipulation causes cross site scripting. The attack may be initiated remotely. In addition, an exploit is available. It is recommended to upgrade the affected component.
Details
A vulnerability classified as critical was found in Yahoo! Messenger 5.5/5.6 (Messaging Software). Affected by this vulnerability is some unknown processing of the file ypager.exe of the component ysmgr URI Handler. The manipulation with an unknown input leads to a cross site scripting vulnerability. The CWE definition for the vulnerability is CWE-80. The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special characters such as "<", ">", and "&" that could be interpreted as web-scripting elements when they are sent to a downstream component that processes web pages. As an impact it is known to affect confidentiality, integrity, and availability.
The weakness was presented 12/05/2003 by Chet Simpson as not defined posting (Bugtraq). The advisory is shared at securityfocus.com. The attack can be launched remotely. It demands that the victim is doing some kind of user interaction. Technical details and also a exploit are known. MITRE ATT&CK project uses the attack technique T1059.007 for this issue.
It is possible to download the exploit at ubabble.com. It is declared as proof-of-concept.
Upgrading to version 5.6 eliminates this vulnerability. Applying a patch is able to eliminate this problem. The bugfix is ready for download at messenger.yahoo.com. The best possible mitigation is suggested to be upgrading to the latest version.
The vulnerability is also documented in the databases at SecurityFocus (BID 9158†), OSVDB (2925†) and Secunia (SA10370†). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
Version
License
Website
- Vendor: https://www.yahoo.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.5VulDB Meta Temp Score: 5.0
VulDB Base Score: 5.5
VulDB Temp Score: 5.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Cross site scriptingCWE: CWE-80 / CWE-74 / CWE-707
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Proof-of-Concept
Download: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Messenger 5.6
Patch: messenger.yahoo.com
Timeline
12/05/2003 🔍12/05/2003 🔍
12/08/2003 🔍
12/08/2003 🔍
12/08/2003 🔍
06/27/2019 🔍
Sources
Vendor: yahoo.comAdvisory: securityfocus.com⛔
Researcher: Chet Simpson
Status: Not defined
GCVE (VulDB): GCVE-100-433
SecurityFocus: 9158 - Yahoo! Messenger IMVironment Cross-Site Scripting Vulnerability
Secunia: 10370 - Yahoo! Messenger IMVironment Cross-Site Scripting Vulnerability, Moderately Critical
OSVDB: 2925 - Yahoo! Messenger IMVironment XSS
Entry
Created: 12/08/2003 17:58Updated: 06/27/2019 12:08
Changes: 12/08/2003 17:58 (64), 06/27/2019 12:08 (1)
Complete: 🔍
Cache ID: 216:D64:103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

No comments yet. Languages: en.
Please log in to comment.