| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 0.00 |
Summary
A vulnerability labeled as problematic has been found in Pidgin 2.0.0. Impacted is an unknown function. Such manipulation leads to resource management. This vulnerability is traded as CVE-2008-2956. There is no exploit available. The presence of this vulnerability remains uncertain at this time.
Details
A vulnerability, which was classified as problematic, has been found in Pidgin 2.0.0 (Messaging Software). Affected by this issue is an unknown part. The manipulation with an unknown input leads to a resource management vulnerability. Using CWE to declare the problem leads to CWE-399. Impacted is availability. CVE summarizes:
** DISPUTED ** Memory leak in Pidgin 2.0.0, and possibly other versions, allows remote attackers to cause a denial of service (memory consumption) via malformed XML documents. NOTE: this issue has been disputed by the upstream vendor, who states: "I was never able to identify a scenario under which a problem occurred and the original reporter wasn t able to supply any sort of reproduction details."
The weakness was shared 07/01/2008 by Andrew (Website). The advisory is shared for download at issues.rpath.com. This vulnerability is handled as CVE-2008-2956 since 07/01/2008. 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 real existence of this vulnerability is still doubted at the moment.
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 SecurityFocus (BID 29985†) and Secunia (SA31387†). The entries VDB-3746, VDB-43093 and VDB-43005 are related to this item. Once again VulDB remains the best source for vulnerability data.
Product
Type
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.3
VulDB Base Score: 5.3
VulDB Temp Score: 5.3
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: Resource managementCWE: CWE-399 / CWE-404
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
05/11/2007 🔍07/01/2008 🔍
07/01/2008 🔍
07/01/2008 🔍
03/17/2015 🔍
08/07/2024 🔍
Sources
Advisory: issues.rpath.com⛔Researcher: Andrew
Status: Not defined
Confirmation: 🔍
Disputed: 🔍
CVE: CVE-2008-2956 (🔍)
GCVE (CVE): GCVE-0-2008-2956
GCVE (VulDB): GCVE-100-43004
SecurityFocus: 29985
Secunia: 31387
See also: 🔍
Entry
Created: 03/17/2015 12:19Updated: 08/07/2024 12:35
Changes: 03/17/2015 12:19 (48), 09/27/2018 09:32 (5), 08/07/2024 12:35 (17)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.