QualityEBiz Quality PPC 1.0 Installation admin.php cpage information disclosure
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in QualityEBiz Quality PPC 1.0. This vulnerability affects unknown code of the file admin.php of the component Installation. Performing a manipulation of the argument cpage results in information disclosure. This vulnerability is reported as CVE-2006-0216. No exploit exists.
Details
A vulnerability, which was classified as problematic, was found in QualityEBiz Quality PPC 1.0. This affects some unknown functionality of the file admin.php of the component Installation. The manipulation of the argument cpage with an unknown input leads to a information disclosure vulnerability. CWE is classifying the issue as CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. This is going to have an impact on confidentiality. The summary by CVE is:
admin.php in QualityEBiz Quality PPC (QPPC) 1.0 build 1644 allows remote attackers to obtain sensitive information, possibly the installation path of the application, via unspecified "meta characters" to the cpage parameter.
The bug was discovered 12/13/2005. The weakness was disclosed 01/13/2006 by Xavier (Website). The advisory is shared at osvdb.org. This vulnerability is uniquely identified as CVE-2006-0216 since 01/16/2006. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1592 for this issue.
The vulnerability was handled as a non-public zero-day exploit for at least 31 days. During that time the estimated underground price was around $0-$5k. By approaching the search of inurl:admin.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 OSVDB (22353†). The entry VDB-28316 is pretty similar. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.3
VulDB Base Score: 5.3
VulDB Temp Score: 5.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: Information disclosureCWE: CWE-200 / CWE-284 / CWE-266
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
12/13/2005 🔍01/13/2006 🔍
01/13/2006 🔍
01/16/2006 🔍
01/16/2006 🔍
03/12/2015 🔍
08/05/2017 🔍
Sources
Advisory: osvdb.org⛔Researcher: Xavier
Status: Not defined
CVE: CVE-2006-0216 (🔍)
GCVE (CVE): GCVE-0-2006-0216
GCVE (VulDB): GCVE-100-28317
OSVDB: 22353 - QualityEBiz Quality PPC admin.php cpage Variable Path Disclosure
See also: 🔍
Entry
Created: 03/12/2015 11:11Updated: 08/05/2017 09:29
Changes: 03/12/2015 11:11 (48), 08/05/2017 09:29 (7)
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.