| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.1 | $0-$5k | 0.00 |
Summary
A vulnerability marked as problematic has been reported in AjaXplorer 2.3.3/2.3.4. Impacted is an unknown function of the file admin.php. This manipulation causes cross-site request forgery. The identification of this vulnerability is CVE-2008-6639. It is possible to initiate the attack remotely. Furthermore, there is an exploit available.
Details
A vulnerability has been found in AjaXplorer 2.3.3/2.3.4 and classified as critical. Affected by this vulnerability is an unknown code of the file admin.php. The manipulation with an unknown input leads to a cross-site request forgery vulnerability. The CWE definition for the vulnerability is CWE-352. The web application does not, or can not, sufficiently verify whether a well-formed, valid, consistent request was intentionally provided by the user who submitted the request. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
Cross-site request forgery (CSRF) vulnerability in admin.php in AjaXplorer 2.3.3 and 2.3.4 allows remote attackers to hijack the authentication of administrators for requests that modify passwords via the update_user_pwd action.
The weakness was shared 05/28/2008 (Website). The advisory is shared at osvdb.org. This vulnerability is known as CVE-2008-6639 since 04/06/2009. The attack can be launched remotely. The exploitation doesn't need any form of authentication. It demands that the victim is doing some kind of user interaction. Technical details and also a exploit are known.
After immediately, there has been an exploit disclosed. It is declared as highly functional. 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 databases at X-Force (42694), OSVDB (45656†) and Secunia (SA30383†). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.3VulDB Meta Temp Score: 6.1
VulDB Base Score: 6.3
VulDB Temp Score: 6.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: Cross-site request forgeryCWE: CWE-352 / CWE-862 / CWE-863
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Highly functional
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: 🔍
Exploit Delay Time: 🔍
Timeline
05/28/2008 🔍05/28/2008 🔍
05/28/2008 🔍
05/28/2008 🔍
04/06/2009 🔍
04/07/2009 🔍
03/17/2015 🔍
11/04/2018 🔍
Sources
Advisory: osvdb.org⛔Status: Not defined
CVE: CVE-2008-6639 (🔍)
GCVE (CVE): GCVE-0-2008-6639
GCVE (VulDB): GCVE-100-47569
X-Force: 42694 - AjaXplorer admin.php cross-site request forgery
Secunia: 30383 - AjaXplorer Password Change Cross-Site Request Forgery, Less Critical
OSVDB: 45656 - AjaXplorer admin.php User Password Modification CSRF
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 03/17/2015 23:38Updated: 11/04/2018 08:32
Changes: 03/17/2015 23:38 (56), 11/04/2018 08:32 (1)
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.