| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, has been found in Vikingboard. This impacts an unknown function of the file cp.php. This manipulation of the argument debug causes information disclosure. This vulnerability is registered as CVE-2007-4089. No exploit is available.
Details
A vulnerability has been found in Vikingboard (Forum Software) (affected version unknown) and classified as problematic. Affected by this vulnerability is an unknown functionality of the file cp.php. The manipulation of the argument debug with an unknown input leads to a information disclosure vulnerability. The CWE definition for the vulnerability is CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. As an impact it is known to affect integrity. The summary by CVE is:
Vikingboard 0.1.2 allows remote attackers to obtain sensitive information via the debug parameter to (1) forum.php, (2) cp.php, and possibly other unspecified components.
The weakness was published 07/25/2007 by Lostmon (Website). The advisory is shared at lostmon.blogspot.com. This vulnerability is known as CVE-2007-4089 since 07/30/2007. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1592 for this issue.
By approaching the search of inurl:cp.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 X-Force (35602), SecurityFocus (BID 25060†), OSVDB (36903†) and Secunia (SA26196†). Similar entries are available at VDB-38097, VDB-38096, VDB-38095 and VDB-85766. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Name
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
07/25/2007 🔍07/25/2007 🔍
07/25/2007 🔍
07/25/2007 🔍
07/30/2007 🔍
07/30/2007 🔍
05/08/2016 🔍
01/06/2019 🔍
Sources
Advisory: lostmon.blogspot.comResearcher: Lostmon
Status: Not defined
CVE: CVE-2007-4089 (🔍)
GCVE (CVE): GCVE-0-2007-4089
GCVE (VulDB): GCVE-100-85765
X-Force: 35602
SecurityFocus: 25060 - Vikingboard Multiple Information Disclosure Weaknesses
Secunia: 26196 - Vikingboard Two Vulnerabilities, Less Critical
OSVDB: 36903 - Vikingboard cp.php debug Variable Information Disclosure
See also: 🔍
Entry
Created: 05/08/2016 22:03Updated: 01/06/2019 10:06
Changes: 05/08/2016 22:03 (57), 01/06/2019 10:06 (3)
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.