| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.8 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Pidgin 2.0.2. It has been classified as very critical. This affects an unknown part of the component Sales. Performing a manipulation results in privilege escalation. This vulnerability is known as CVE-2007-3841. No exploit is available.
Details
A vulnerability, which was classified as very critical, was found in Pidgin 2.0.2 (Messaging Software). This affects an unknown code block of the component Sales. The manipulation with an unknown input leads to a privilege escalation vulnerability. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
Unspecified vulnerability in Pidgin (formerly Gaim) 2.0.2 for Linux allows remote authenticated users, who are listed in a users list, to execute certain commands via unspecified vectors, aka ZD-00000035. NOTE: this information is based upon a vague advisory by a vulnerability information sales organization that does not coordinate with vendors or release actionable advisories. A CVE has been assigned for tracking purposes, but duplicates with other CVEs are difficult to determine.
The weakness was published 07/17/2007 (Website). It is possible to read the advisory at wslabi.com. This vulnerability is uniquely identified as CVE-2007-3841 since 07/17/2007. The exploitability is told to be easy. It is possible to initiate the attack remotely. The requirement for exploitation is a authentication. The technical details are unknown and an exploit is not publicly available. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 09/05/2018).
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 vulnerability database at SecurityFocus (BID 24904†). Similar entries are available at VDB-38007 and VDB-37712. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.8VulDB Meta Temp Score: 8.8
VulDB Base Score: 8.8
VulDB Temp Score: 8.8
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: Privilege escalationCWE: Unknown
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
07/13/2007 🔍07/17/2007 🔍
07/17/2007 🔍
07/17/2007 🔍
03/15/2015 🔍
09/05/2018 🔍
Sources
Advisory: wslabi.comStatus: Not defined
CVE: CVE-2007-3841 (🔍)
GCVE (CVE): GCVE-0-2007-3841
GCVE (VulDB): GCVE-100-37875
SecurityFocus: 24904 - Pidgin Unspecified Remote Command Execution Vulnerability
See also: 🔍
Entry
Created: 03/15/2015 15:58Updated: 09/05/2018 10:30
Changes: 03/15/2015 15:58 (46), 09/05/2018 10:30 (3)
Complete: 🔍
Cache ID: 216:0AF: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.