VolksBank Online Banking Vorlagen Gruppen Name Persistent cross site scripting
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.2 | $0-$5k | 0.00 |
Summary
A vulnerability was found in VolksBank Online Banking. It has been classified as problematic. This affects an unknown function of the component Vorlagen Gruppen Name. Performing a manipulation results in cross site scripting (Persistent). The attack can be initiated remotely. There is not any exploit available. Applying a patch is the recommended action to fix this issue.
Details
A vulnerability classified as problematic has been found in VolksBank Online Banking (Banking Software) (unknown version). This affects an unknown code block of the component Vorlagen Gruppen Name. The manipulation with an unknown input leads to a cross site scripting vulnerability (Persistent). CWE is classifying the issue as CWE-80. The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special characters such as "<", ">", and "&" that could be interpreted as web-scripting elements when they are sent to a downstream component that processes web pages. This is going to have an impact on integrity.
The weakness was released 02/07/2012 as VL-ID 172 as not defined advisory (Website). The advisory is shared at vulnerability-lab.com. The exploitability is told to be easy. It is possible to initiate the attack remotely. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1059.007 for this issue.
The vulnerability was handled as a non-public zero-day exploit for at least 219 days. During that time the estimated underground price was around $0-$5k.
Applying a patch is able to eliminate this problem.
Entries connected to this vulnerability are available at VDB-91340, VDB-91342, VDB-91343 and VDB-91344. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.5VulDB Meta Temp Score: 3.2
VulDB Base Score: 3.5
VulDB Temp Score: 3.2
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: PersistentClass: Cross site scripting / Persistent
CWE: CWE-80 / CWE-74 / CWE-707
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
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: PatchStatus: 🔍
0-Day Time: 🔍
Timeline
07/03/2011 🔍02/07/2012 🔍
09/08/2016 🔍
04/11/2019 🔍
Sources
Advisory: VL-ID 172Status: Not defined
GCVE (VulDB): GCVE-100-91341
See also: 🔍
Entry
Created: 09/08/2016 09:08Updated: 04/11/2019 18:15
Changes: 09/08/2016 09:08 (41), 04/11/2019 18:15 (2)
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.