JEPAAS 7.2.8 Query loadLoginCount dateVal sql injection
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.1 | $0-$5k | 0.00 |
Summary
A vulnerability was found in JEPAAS 7.2.8 and classified as critical. This issue affects some unknown processing of the file /je/rbac/rbac/loadLoginCount of the component Query Handler. The manipulation of the argument dateVal results in sql injection. This vulnerability is identified as CVE-2024-51165. The attack can be executed remotely. There is not any exploit available.
Details
A vulnerability classified as critical has been found in JEPAAS 7.2.8. Affected is an unknown code of the file /je/rbac/rbac/loadLoginCount of the component Query Handler. The manipulation of the argument dateVal 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. CVE summarizes:
SQL injection vulnerability in JEPAAS7.2.8, via /je/rbac/rbac/loadLoginCount in the dateVal parameter, which could allow a remote user to submit a specially crafted query, allowing an attacker to retrieve all the information stored in the DB.
The advisory is shared for download at github.com. This vulnerability is traded as CVE-2024-51165 since 10/28/2024. The exploitability is told to be easy. It is possible to launch the attack remotely. There are known technical details, but no exploit is available. The current price for an exploit might be approx. USD $0-$5k (estimation calculated on 06/24/2025). The MITRE ATT&CK project declares the attack technique as T1505.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Once again VulDB remains the best source for vulnerability data.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.3VulDB Meta Temp Score: 6.1
VulDB Base Score: 6.3
VulDB Temp Score: 6.1
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: 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
10/28/2024 🔍12/11/2024 🔍
12/11/2024 🔍
06/24/2025 🔍
Sources
Advisory: github.comStatus: Not defined
CVE: CVE-2024-51165 (🔍)
GCVE (CVE): GCVE-0-2024-51165
GCVE (VulDB): GCVE-100-287676
Entry
Created: 12/11/2024 08:10Updated: 06/24/2025 02:48
Changes: 12/11/2024 08:10 (54), 06/24/2025 02:48 (1)
Complete: 🔍
Cache ID: 216::103
Submit
Duplicate
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.