Bloo 1.0 phoo.base.php descriptorfilelist file inclusion ⚔ [Disputed]
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.3 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical was found in Bloo 1.0. Affected is an unknown function of the file phoo.base.php. Such manipulation of the argument descriptorfilelist leads to file inclusion. This vulnerability is uniquely identified as CVE-2006-6023. No exploit exists. It is still unclear if this vulnerability genuinely exists.
Details
A vulnerability was found in Bloo 1.0. It has been rated as critical. Affected by this issue is an unknown function of the file phoo.base.php. The manipulation of the argument descriptorfilelist with an unknown input leads to a file inclusion vulnerability. Using CWE to declare the problem leads to CWE-73. The product allows user input to control or influence paths or file names that are used in filesystem operations. Impacted is confidentiality, integrity, and availability. CVE summarizes:
PHP remote file inclusion vulnerability in phoo.base.php in Bill Roberts Bloo 1.0 allows remote attackers to execute arbitrary PHP code via a URL in the descriptorFileList parameter. NOTE: this issue is disputed by CVE since $descriptorFileList is used in a function definition within phoo.base.php
The weakness was disclosed 11/21/2006 (Website). The advisory is available at securityfocus.com. This vulnerability is handled as CVE-2006-6023 since 11/21/2006. The exploitation is known to be easy. The attack may be launched remotely. No form of authentication is required for exploitation. Technical details are known, but there is no available exploit.
The real existence of this vulnerability is still doubted at the moment. By approaching the search of inurl:phoo.base.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 vulnerability database at X-Force (30336). The entry VDB-33358 is pretty similar. If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 7.3
VulDB Base Score: 7.3
VulDB Temp Score: 7.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: File inclusionCWE: CWE-73
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
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/21/2006 🔍11/21/2006 🔍
11/21/2006 🔍
03/12/2015 🔍
04/28/2026 🔍
Sources
Advisory: securityfocus.com⛔Status: Not defined
Disputed: 🔍
CVE: CVE-2006-6023 (🔍)
GCVE (CVE): GCVE-0-2006-6023
GCVE (VulDB): GCVE-100-33362
X-Force: 30336
See also: 🔍
Entry
Created: 03/12/2015 22:21Updated: 04/28/2026 01:48
Changes: 03/12/2015 22:21 (47), 08/14/2018 08:20 (2), 08/08/2024 11:37 (17), 04/28/2026 01:48 (2)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.