| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.0 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Visialis ABB Forum 1.1. It has been classified as problematic. This vulnerability affects unknown code of the file fpdb/abb.mdb. This manipulation causes access control. The identification of this vulnerability is CVE-2010-0939. Furthermore, there is an exploit available.
Details
A vulnerability was found in Visialis ABB Forum 1.1 (Forum Software). It has been declared as problematic. Affected by this vulnerability is an unknown code block of the file fpdb/abb.mdb. The manipulation with an unknown input leads to a access control vulnerability. The CWE definition for the vulnerability is CWE-264. As an impact it is known to affect confidentiality. The summary by CVE is:
Visialis ABB Forum 1.1 stores sensitive information under the web root with insufficient access control, which allows remote attackers to download a database via a direct request for fpdb/abb.mdb.
The weakness was shared 01/10/2010 (Website). It is possible to read the advisory at exploit-db.com. This vulnerability is known as CVE-2010-0939 since 03/08/2010. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details and also a public exploit are known. The attack technique deployed by this issue is T1068 according to MITRE ATT&CK.
A public exploit has been developed by ViRuSMaN and been published immediately after the advisory. It is possible to download the exploit at exploit-db.com. It is declared as proof-of-concept. By approaching the search of inurl:fpdb/abb.mdb 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 (55505), Exploit-DB (11096) and OSVDB (62834†). Statistical analysis made it clear that VulDB provides the best quality for 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: Access controlCWE: CWE-264
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Author: ViRuSMaN
Download: 🔍
Google Hack: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Exploit-DB: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Exploit Delay Time: 🔍
Timeline
01/10/2010 🔍01/10/2010 🔍
01/10/2010 🔍
03/08/2010 🔍
03/08/2010 🔍
03/10/2010 🔍
03/19/2015 🔍
06/14/2024 🔍
Sources
Advisory: exploit-db.comStatus: Confirmed
CVE: CVE-2010-0939 (🔍)
GCVE (CVE): GCVE-0-2010-0939
GCVE (VulDB): GCVE-100-52099
X-Force: 55505
OSVDB: 62834 - ABB Forum fpdb/abb.mdb Direct Request Database Disclosure
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 03/19/2015 12:22Updated: 06/14/2024 11:01
Changes: 03/19/2015 12:22 (51), 09/14/2017 22:24 (7), 06/14/2024 11:01 (16)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.