| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.9 | $0-$5k | 0.00 |
Summary
A vulnerability labeled as critical has been found in Yahoo! Messenger. This issue affects some unknown processing. Such manipulation of the argument TargetName leads to memory corruption. It is possible to launch the attack remotely. Furthermore, an exploit is available. Disabling the affected component is advisable.
Details
A vulnerability, which was classified as critical, has been found in Yahoo! Messenger (Messaging Software) (the affected version unknown). Affected by this issue is an unknown part. The manipulation of the argument TargetName with an unknown input leads to a memory corruption vulnerability. Using CWE to declare the problem leads to CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. Impacted is confidentiality, integrity, and availability.
The bug was discovered 09/16/2003. The weakness was published 09/18/2003 by Cesar Cerrudo (Website). The advisory is available at messenger.yahoo.com. The attack may be launched remotely. No form of authentication is required for exploitation. Technical details as well as a public exploit are known.
After before and not just, there has been an exploit disclosed. The exploit is available at securiteam.com. It is declared as proof-of-concept. The vulnerability was handled as a non-public zero-day exploit for at least 2 days. During that time the estimated underground price was around $5k-$25k.
Applying a patch is able to eliminate this problem. The bugfix is ready for download at messenger.yahoo.com.
The vulnerability is also documented in the databases at X-Force (13210), SecurityFocus (BID 8634†), OSVDB (2566†) and Secunia (SA9760†). Similar entries are available at VDB-291 and VDB-2335. If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Type
Vendor
Name
License
Website
- Vendor: https://www.yahoo.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 6.9
VulDB Base Score: 7.3
VulDB Temp Score: 6.9
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: Memory corruptionCWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Access: Public
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: DisableStatus: 🔍
0-Day Time: 🔍
Patch: messenger.yahoo.com
Timeline
09/16/2003 🔍09/16/2003 🔍
09/16/2003 🔍
09/17/2003 🔍
09/18/2003 🔍
09/19/2003 🔍
06/26/2019 🔍
Sources
Vendor: yahoo.comAdvisory: messenger.yahoo.com
Researcher: Cesar Cerrudo
Status: Confirmed
GCVE (VulDB): GCVE-100-290
X-Force: 13210 - Yahoo! Webcam Viewer Wrapper ActiveX buffer overflow, High Risk
SecurityFocus: 8634 - Yahoo! Webcam ActiveX Control Buffer Overrun Vulnerability
Secunia: 9760 - Yahoo! Chat and Messenger Stack and Heap Overflows, Highly Critical
OSVDB: 2566 - Yahoo! Chat / Messenger Multiple Parameter Remote Overflows
SecuriTeam: securiteam.com
scip Labs: https://www.scip.ch/en/?labs.20161013
See also: 🔍
Entry
Created: 09/19/2003 13:26Updated: 06/26/2019 15:38
Changes: 09/19/2003 13:26 (68), 06/26/2019 15:38 (2)
Complete: 🔍
Cache ID: 216:D24:103
If you want to get best quality of vulnerability data, you may have to visit VulDB.

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