Fusion PHP-Fusion up to 6.00.206 subheader.php information disclosure
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.0 | $0-$5k | 0.00 |
Summary
A vulnerability marked as problematic has been reported in Fusion PHP-Fusion up to 6.00.206. Affected by this issue is some unknown functionality of the file subheader.php. The manipulation leads to information disclosure. This vulnerability is uniquely identified as CVE-2005-3739. No exploit exists.
Details
A vulnerability was found in Fusion PHP-Fusion up to 6.00.206 (Content Management System). It has been rated as problematic. This issue affects an unknown code of the file subheader.php. 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 summary by CVE is:
Unspecified vulnerability in subheader.php in PHP-Fusion 6.00.206 and earlier allows remote attackers to obtain the full path via unspecified vectors.
The weakness was disclosed 11/18/2005 by Robin Verton (Website). The advisory is shared at secunia.com. The identification of this vulnerability is CVE-2005-3739 since 11/22/2005. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1592 for this issue.
It is declared as proof-of-concept. By approaching the search of inurl:subheader.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 OSVDB (20990†) and Secunia (SA17664†). The entries VDB-27018 and VDB-83174 are pretty similar. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
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.0
VulDB Base Score: 5.3
VulDB Temp Score: 5.0
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: Information disclosureCWE: CWE-200 / CWE-284 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Proof-of-Concept
Google Hack: 🔍
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/18/2005 🔍11/21/2005 🔍
11/21/2005 🔍
11/22/2005 🔍
11/22/2005 🔍
03/11/2015 🔍
07/30/2017 🔍
Sources
Advisory: secunia.com⛔Researcher: Robin Verton
Status: Not defined
CVE: CVE-2005-3739 (🔍)
GCVE (CVE): GCVE-0-2005-3739
GCVE (VulDB): GCVE-100-27017
Secunia: 17664 - PHP-Fusion SQL Injection Vulnerabilities, Moderately Critical
OSVDB: 20990 - PHP-Fusion subheader.php Path Disclosure
Vupen: ADV-2005-2504
See also: 🔍
Entry
Created: 03/11/2015 23:39Updated: 07/30/2017 11:31
Changes: 03/11/2015 23:39 (49), 07/30/2017 11:31 (7)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.