mglowinski93 FinanseWebApplication balance.php startDate/endDate sql injection
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical has been found in mglowinski93 FinanseWebApplication. The impacted element is an unknown function of the file balance.php. Performing a manipulation of the argument startDate/endDate results in sql injection. There is not any exploit available. Continious delivery with rolling releases is used by this product. Therefore, no version details of affected nor updated releases are available. Applying a patch is the recommended action to fix this issue.
Details
A vulnerability, which was classified as critical, was found in mglowinski93 FinanseWebApplication (version now known). This affects some unknown processing of the file balance.php. The manipulation of the argument startDate/endDate with an unknown input leads to a sql injection vulnerability. CWE is classifying the issue as CWE-89. The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. This is going to have an impact on confidentiality, integrity, and availability.
The weakness was released 09/22/2020. The advisory is shared at github.com. The exploitability is told to be easy. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1505 for this issue.
By approaching the search of inurl:balance.php it is possible to find vulnerable targets with Google Hacking.
Applying the patch aa432c7b118d56c20aa9298d1d34991e5c9fc1cc is able to eliminate this problem. The bugfix is ready for download at github.com. A possible mitigation has been published immediately after the disclosure of the vulnerability. The advisory contains the following remark:
prevent balance.php before SQL injection
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
License
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.5VulDB Meta Temp Score: 5.3
VulDB Base Score: 5.5
VulDB Temp Score: 5.3
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
Class: Sql injectionCWE: CWE-89 / CWE-74 / CWE-707
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Partially
Availability: 🔍
Status: Not defined
Google Hack: 🔍
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: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Patch: aa432c7b118d56c20aa9298d1d34991e5c9fc1cc
Timeline
09/22/2020 🔍09/22/2020 🔍
03/23/2024 🔍
03/23/2024 🔍
Sources
Product: github.comAdvisory: github.com
Status: Confirmed
CVE: Not possible due to CNA Operational Rules
GCVE (VulDB): GCVE-100-257781
Entry
Created: 03/23/2024 10:39Changes: 03/23/2024 10:39 (57)
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.