| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.0 | $0-$5k | 0.00 |
Summary
A vulnerability marked as problematic has been reported in Yahoo Messenger 5.5/5.6/6.0. This affects an unknown part of the component URL Handler. This manipulation causes denial of service. This vulnerability is registered as CVE-2005-1618. Furthermore, an exploit is available.
Details
A vulnerability was found in Yahoo Messenger 5.5/5.6/6.0 (Messaging Software). It has been declared as problematic. Affected by this vulnerability is an unknown code of the component URL Handler. The manipulation with an unknown input leads to a denial of service vulnerability. The CWE definition for the vulnerability is CWE-404. The product does not release or incorrectly releases a resource before it is made available for re-use. As an impact it is known to affect availability. The summary by CVE is:
The YMSGR URL handler in Yahoo! Messenger 5.x through 6.0 allows remote attackers to cause a denial of service (disconnect) via a room login or a room join request packet with a third : (colon) and an & (ampersand), which causes Messenger to send a corrupted packet to the server, which triggers a disconnect from the server.
The weakness was published 05/14/2005 by Torseq Tech. with Shell as not defined posting (Bugtraq). The advisory is shared at marc.theaimsgroup.com. This vulnerability is known as CVE-2005-1618. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details are unknown but an exploit is available.
After immediately, there has been an exploit disclosed. It is declared as proof-of-concept.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the databases at X-Force (20593), SecurityFocus (BID 13626†), OSVDB (16816†) and Vulnerability Center (SBV-29215†). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.0
VulDB Base Score: 5.3
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: 🔍
NVD Base Score: 🔍
Exploiting
Class: Denial of serviceCWE: CWE-404
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Proof-of-Concept
EPSS Score: 🔍
EPSS Percentile: 🔍
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Exploit Delay Time: 🔍
PaloAlto IPS: 🔍
Timeline
05/13/2005 🔍05/13/2005 🔍
05/14/2005 🔍
05/14/2005 🔍
05/16/2005 🔍
05/16/2005 🔍
05/21/2005 🔍
01/18/2011 🔍
03/11/2015 🔍
07/05/2021 🔍
Sources
Advisory: marc.theaimsgroup.comResearcher: Torseq Tech.
Organization: Shell
Status: Not defined
CVE: CVE-2005-1618 (🔍)
GCVE (CVE): GCVE-0-2005-1618
GCVE (VulDB): GCVE-100-25225
X-Force: 20593
SecurityFocus: 13626 - Yahoo! Messenger URL Handler Remote Denial Of Service Vulnerability
OSVDB: 16816 - Yahoo! Messenger URL Handler Remote DoS
Vulnerability Center: 29215 - Yahoo! Messenger 5.0 Through 6.0 Remote DoS Vulnerability, Medium
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 03/11/2015 11:41Updated: 07/05/2021 08:54
Changes: 03/11/2015 11:41 (56), 03/13/2017 10:05 (10), 07/05/2021 08:54 (3)
Complete: 🔍
Cache ID: 216::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.