| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.0 | $0-$5k | 0.00 |
Summary
A vulnerability marked as critical has been reported in Yahoo! Messenger. Impacted is an unknown function. Performing a manipulation of the argument AppId results in memory corruption. The attack can be initiated remotely. Additionally, an exploit exists. Disabling the affected component is recommended.
Details
A vulnerability, which was classified as critical, was found in Yahoo! Messenger (Messaging Software) (the affected version is unknown). This affects an unknown code. The manipulation of the argument AppId with an unknown input leads to a memory corruption vulnerability. CWE is classifying the issue as 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. This is going to have an impact on confidentiality, integrity, and availability.
The weakness was released 09/18/2003 by Cesar Cerrudo (Website). It is possible to read the advisory at messenger.yahoo.com. It is possible to initiate the attack remotely. Technical details and a exploit are known.
The exploit is shared for download at securiteam.com. It is declared as proof-of-concept. We expect the 0-day to have been worth approximately $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 vulnerability database at Secunia (SA9760†). Entries connected to this vulnerability are available at VDB-290 and VDB-2335. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
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: 6.3VulDB Meta Temp Score: 6.0
VulDB Base Score: 6.3
VulDB Temp Score: 6.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: Memory corruptionCWE: CWE-119
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: DisableStatus: 🔍
0-Day Time: 🔍
Patch: messenger.yahoo.com
Timeline
09/18/2003 🔍09/19/2003 🔍
06/26/2019 🔍
Sources
Vendor: yahoo.comAdvisory: messenger.yahoo.com
Researcher: Cesar Cerrudo
Status: Not defined
GCVE (VulDB): GCVE-100-291
Secunia: 9760 - Yahoo! Chat and Messenger Stack and Heap Overflows, Highly Critical
SecuriTeam: securiteam.com
See also: 🔍
Entry
Created: 09/19/2003 16:17Updated: 06/26/2019 15:13
Changes: 09/19/2003 16:17 (49), 06/26/2019 15:13 (5)
Complete: 🔍
Cache ID: 216:93A:103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.