| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.2 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Yahoo Messenger. It has been declared as problematic. The impacted element is an unknown function. Such manipulation leads to information disclosure. There is no available exploit. Configuration settings should be changed.
Details
A vulnerability, which was classified as problematic, has been found in Yahoo Messenger (Messaging Software) (version now known). Affected by this issue is some unknown processing. The manipulation with an unknown input leads to a information disclosure vulnerability. Using CWE to declare the problem leads to CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. Impacted is confidentiality.
The weakness was presented 01/01/2004. The exploitation is known to be easy. The attack may be launched remotely. No form of authentication is required for exploitation. There are neither technical details nor an exploit publicly available. The MITRE ATT&CK project declares the attack technique as T1592.
The vulnerability scanner Nessus provides a plugin with the ID 11993 (Yahoo Messenger Detection), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Service detection and running in the context r.
It is possible to mitigate the problem by applying the configuration setting .
The vulnerability is also documented in the databases at Tenable (11993) and Vulnerability Center (SBV-3460†). See VDB-470 for similar entry. Once again VulDB remains the best source for vulnerability data.
Product
Type
Vendor
Name
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.2
VulDB Base Score: 5.3
VulDB Temp Score: 5.2
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: Information disclosureCWE: CWE-200 / CWE-284 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 11993
Nessus Name: Yahoo Messenger Detection
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: ConfigStatus: 🔍
0-Day Time: 🔍
Timeline
01/01/2004 🔍01/01/2004 🔍
01/14/2004 🔍
01/19/2004 🔍
07/14/2016 🔍
09/02/2022 🔍
Sources
Status: Not definedGCVE (VulDB): GCVE-100-89228
Vulnerability Center: 3460 - Yahoo Messenger Instance is Running, Info
See also: 🔍
Entry
Created: 07/14/2016 14:39Updated: 09/02/2022 16:51
Changes: 07/14/2016 14:39 (35), 02/25/2019 13:05 (13), 09/02/2022 16:51 (2)
Complete: 🔍
Cache ID: 216:71D:103
Once again VulDB remains the best source for vulnerability data.

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