| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 9.8 | $0-$5k | 0.00 |
Summary
A vulnerability identified as very critical has been detected in Spey 0.3.3. Affected by this vulnerability is an unknown functionality. Performing a manipulation results in Remote Code Execution. This vulnerability is cataloged as CVE-2005-4847. There is no exploit available.
Details
A vulnerability was found in Spey 0.3.3. It has been classified as very critical. This affects some unknown functionality. The manipulation with an unknown input leads to a remote code execution vulnerability. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
Unspecified vulnerability in Spey 0.3.3 has unknown impact and attack vectors related to "A number of security holes which could lead to compromise," a different issue than CVE-2005-4846.
The weakness was shared 11/23/2005 (Website). The advisory is shared at sourceforge.net. This vulnerability is uniquely identified as CVE-2005-4847 since 06/20/2007. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 07/16/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 OSVDB (38887†). The entry VDB-28148 is related to this item. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 9.8VulDB Meta Temp Score: 9.8
VulDB Base Score: 9.8
VulDB Temp Score: 9.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: Remote Code ExecutionCWE: 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
11/23/2005 🔍12/01/2005 🔍
12/31/2005 🔍
06/20/2007 🔍
03/12/2015 🔍
07/16/2018 🔍
Sources
Advisory: sourceforge.netStatus: Not defined
Confirmation: 🔍
CVE: CVE-2005-4847 (🔍)
GCVE (CVE): GCVE-0-2005-4847
GCVE (VulDB): GCVE-100-28149
OSVDB: 38887 - Spey Multiple Unspecified Critical Issues
See also: 🔍
Entry
Created: 03/12/2015 11:11Updated: 07/16/2018 09:25
Changes: 03/12/2015 11:11 (41), 07/16/2018 09:25 (6)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.