| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.5 | $0-$5k | 0.75 |
Summary
A vulnerability marked as critical has been reported in Yahoo! Messenger 4.0/5.0/5.5. Impacted is an unknown function of the component Signature Handler. The manipulation leads to access control. This vulnerability is listed as CVE-2002-2361. There is no available exploit.
Details
A vulnerability was found in Yahoo! Messenger 4.0/5.0/5.5 (Messaging Software) and classified as critical. This issue affects an unknown code of the component Signature Handler. The manipulation with an unknown input leads to a access control vulnerability. Using CWE to declare the problem leads to CWE-264. Impacted is confidentiality, and integrity. The summary by CVE is:
The installer in Yahoo! Messenger 4.0, 5.0 and 5.5 does not verify package signatures which could allow remote attackers to install trojan programs via DNS spoofing.
The weakness was presented 12/31/2002 (Website). It is possible to read the advisory at cert.uni-stuttgart.de. The identification of this vulnerability is CVE-2002-2361 since 10/29/2007. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1068 according to MITRE ATT&CK.
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 (9984) and SecurityFocus (BID 5579†). Statistical analysis made it clear that VulDB provides the best quality for 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: 6.5VulDB Meta Temp Score: 6.5
VulDB Base Score: 6.5
VulDB Temp Score: 6.5
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: Access controlCWE: CWE-264
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
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: 🔍
Timeline
08/27/2002 🔍12/31/2002 🔍
12/31/2002 🔍
10/29/2007 🔍
08/07/2014 🔍
07/14/2024 🔍
Sources
Vendor: yahoo.comAdvisory: cert.uni-stuttgart.de
Status: Not defined
CVE: CVE-2002-2361 (🔍)
GCVE (CVE): GCVE-0-2002-2361
GCVE (VulDB): GCVE-100-20003
X-Force: 9984
SecurityFocus: 5579 - Yahoo Instant Messenger Signed Content Weakness
Entry
Created: 08/07/2014 13:25Updated: 07/14/2024 03:43
Changes: 08/07/2014 13:25 (49), 06/12/2018 11:05 (2), 07/14/2024 03:43 (17)
Complete: 🔍
Cache ID: 216::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.