TKS Banking Solutions ePortfolio 1.0 cross-site request forgery
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.8 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, has been found in TKS Banking Solutions ePortfolio 1.0. This affects an unknown function. Performing a manipulation results in cross-site request forgery. This vulnerability is known as CVE-2007-1332. Remote exploitation of the attack is possible. No exploit is available.
Details
A vulnerability classified as critical has been found in TKS Banking Solutions ePortfolio 1.0 (Banking Software). This affects an unknown functionality. The manipulation with an unknown input leads to a cross-site request forgery vulnerability. CWE is classifying the issue as 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. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
Multiple cross-site request forgery (CSRF) vulnerabilities in TKS Banking Solutions ePortfolio 1.0 Java allow remote attackers to perform unspecified restricted actions in the context of certain accounts by bypassing the client-side protection scheme.
The weakness was published 03/07/2007 by Stefan Friedli (Website). The advisory is shared at securityfocus.com. This vulnerability is uniquely identified as CVE-2007-1332 since 03/07/2007. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available.
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 SecurityFocus (BID 22829†) and Secunia (SA24331†). Similar entry is available at VDB-35504. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.8VulDB Meta Temp Score: 8.8
VulDB Base Score: 8.8
VulDB Temp Score: 8.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: 🔍
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: Not defined
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
03/05/2007 🔍03/07/2007 🔍
03/07/2007 🔍
03/07/2007 🔍
03/08/2007 🔍
03/13/2015 🔍
08/26/2018 🔍
Sources
Advisory: securityfocus.com⛔Researcher: Stefan Friedli
Status: Not defined
CVE: CVE-2007-1332 (🔍)
GCVE (CVE): GCVE-0-2007-1332
GCVE (VulDB): GCVE-100-35505
SecurityFocus: 22829 - EPortfolio Client Side Input Validation Vulnerability
Secunia: 24331 - ePortfolio Various Input Validation Vulnerabilities, Moderately Critical
See also: 🔍
Entry
Created: 03/13/2015 12:16Updated: 08/26/2018 09:39
Changes: 03/13/2015 12:16 (50), 08/26/2018 09:39 (6)
Complete: 🔍
Cache ID: 216:E94: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.