DataEase up to 2.4.x getEngine.js information disclosure
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.1 | $0-$5k | 0.00 |
Summary
A vulnerability was found in DataEase up to 2.4.x. It has been rated as problematic. This impacts an unknown function of the file /de2api/engine/getEngine.js. The manipulation leads to information disclosure. This vulnerability is listed as CVE-2024-30269. The attack may be initiated remotely. In addition, an exploit is available. Upgrading the affected component is advised.
Details
A vulnerability was found in DataEase up to 2.4.x and classified as problematic. This issue affects an unknown function of the file /de2api/engine/getEngine.js. The manipulation with an unknown input leads to a information disclosure vulnerability. Using CWE to declare the problem leads to CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. Impacted is confidentiality. The summary by CVE is:
DataEase, an open source data visualization and analysis tool, has a database configuration information exposure vulnerability prior to version 2.5.0. Visiting the `/de2api/engine/getEngine;.js` path via a browser reveals that the platform's database configuration is returned. The vulnerability has been fixed in v2.5.0. No known workarounds are available aside from upgrading.
It is possible to read the advisory at github.com. The identification of this vulnerability is CVE-2024-30269 since 03/26/2024. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details as well as a public exploit are known. The attack technique deployed by this issue is T1592 according to MITRE ATT&CK.
The exploit is available at exploit-db.com. It is declared as proof-of-concept.
Upgrading to version 2.5.0 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at Exploit-DB (52128). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Name
Version
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.1
VulDB Base Score: 5.3
VulDB Temp Score: 4.8
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.3
NVD Vector: 🔍
CNA Base Score: 5.3
CNA Vector (GitHub, Inc.): 🔍
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: Information disclosureCWE: CWE-200 / CWE-284 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Exploit-DB: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: DataEase 2.5.0
Timeline
03/26/2024 🔍04/08/2024 🔍
04/08/2024 🔍
04/10/2025 🔍
Sources
Product: github.comAdvisory: GHSA-8gvx-4qvj-6vv5
Status: Confirmed
CVE: CVE-2024-30269 (🔍)
GCVE (CVE): GCVE-0-2024-30269
GCVE (VulDB): GCVE-100-259763
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 04/08/2024 16:48Updated: 04/10/2025 20:22
Changes: 04/08/2024 16:48 (62), 05/10/2024 16:04 (2), 05/10/2024 16:10 (1), 02/13/2025 03:10 (11), 04/10/2025 20:22 (11)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.