| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.1 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in TorrentFlux 2.2 and classified as problematic. The impacted element is an unknown function of the file index.php. Performing a manipulation of the argument delfile results in an unknown weakness. This vulnerability is known as CVE-2006-6329. Furthermore, an exploit is available.
Details
A vulnerability, which was classified as problematic, was found in TorrentFlux 2.2 (Peer-to-Peer Software). This affects an unknown part of the file index.php. The manipulation of the argument delfile with an unknown input leads to a unknown weakness. This is going to have an impact on integrity, and availability. The summary by CVE is:
index.php for TorrentFlux 2.2 allows remote attackers to delete files by specifying the target filename in the delfile parameter.
The weakness was published 12/06/2006 (Website). The advisory is shared at secunia.com. This vulnerability is uniquely identified as CVE-2006-6329 since 12/06/2006. It is possible to initiate the attack remotely. A authentication is necessary for exploitation. Technical details and a public exploit are known.
A public exploit has been developed by r0ut3r and been published even before and not after the advisory. The exploit is shared for download at exploit-db.com. It is declared as proof-of-concept. The vulnerability was handled as a non-public zero-day exploit for at least 21 days. During that time the estimated underground price was around $0-$5k. By approaching the search of inurl:index.php it is possible to find vulnerable targets with Google Hacking.
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 Exploit-DB (2786) and Secunia (SA22880†). Similar entries are available at VDB-33888, VDB-33647, VDB-33646 and VDB-33644. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.4VulDB Meta Temp Score: 5.1
VulDB Base Score: 5.4
VulDB Temp Score: 5.1
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: UnknownCWE: Unknown
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Author: r0ut3r
Download: 🔍
Google Hack: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Exploit-DB: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
11/14/2006 🔍11/14/2006 🔍
11/15/2006 🔍
12/06/2006 🔍
12/06/2006 🔍
12/06/2006 🔍
03/12/2015 🔍
08/08/2024 🔍
Sources
Advisory: secunia.com⛔Status: Confirmed
Confirmation: 🔍
CVE: CVE-2006-6329 (🔍)
GCVE (CVE): GCVE-0-2006-6329
GCVE (VulDB): GCVE-100-33645
Secunia: 22880 - TorrentFlux Arbitrary Command Execution And Directory Traversal, Moderately Critical
scip Labs: https://www.scip.ch/en/?labs.20161013
See also: 🔍
Entry
Created: 03/12/2015 22:21Updated: 08/08/2024 03:06
Changes: 03/12/2015 22:21 (45), 08/09/2018 07:37 (14), 08/08/2024 03:06 (17)
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.