| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.8 | $0-$5k | 0.00 |
Summary
A vulnerability was found in XTB Trade Brokers v4.x. It has been rated as problematic. This vulnerability affects unknown code of the file xtb_v4.x. This manipulation causes memory corruption (Pointer). Furthermore, an exploit is available.
Details
A vulnerability was found in XTB Trade Brokers v4.x. It has been declared as problematic. Affected by this vulnerability is an unknown function of the file xtb_v4.x. The manipulation with an unknown input leads to a memory corruption vulnerability (Pointer). The CWE definition for the vulnerability is CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. As an impact it is known to affect confidentiality, integrity, and availability.
The weakness was published 07/29/2011 as VL-ID 41 as not defined advisory (Website). The advisory is shared at vulnerability-lab.com. An attack has to be approached locally. The successful exploitation requires a single authentication. Technical details and also a public exploit are known.
After immediately, there has been an exploit disclosed. It is possible to download the exploit at vulnerability-lab.com. It is declared as proof-of-concept.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
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: 4.8
VulDB Base Score: 5.3
VulDB Temp Score: 4.8
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: 🔍
Exploiting
Name: PointerClass: Memory corruption / Pointer
CWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: No
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍
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
07/29/2011 🔍07/29/2011 🔍
09/06/2016 🔍
04/09/2019 🔍
Sources
Advisory: VL-ID 41Status: Not defined
GCVE (VulDB): GCVE-100-91105
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 09/06/2016 11:33Updated: 04/09/2019 17:23
Changes: 09/06/2016 11:33 (43), 04/09/2019 17:23 (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.