CVE-2024-30269: CVE-2024-30269: DataEase, an open source data visualization and analysis tool, has a database configuratio…
dataease · dataease · NVD published 2024-04-08 · posted 2025-04-06 · last modified 2026-06-17
What it 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.
| Weakness | CWE-200 |
|---|---|
| CVSS vector | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N (source: [email protected]) |
| ATT&CK tactics | Collection |
Exploitation evidence
First exploit evidence seen: 2025-04-06 (earliest date across the sources below).
Exploited in the wild
No source on this site lists in-the-wild exploitation yet (CISA KEV, VulnCheck KEV).
Public exploit code
Exploit-DB
- EDB-52128: DataEase 2.4.0 - Database Configuration Information Exposure (2025-04-06)
Sources: Exploit-DB (OffSec).
Defend the Chain
The attack chain for CVE-2024-30269 laid across the MITRE ATT&CK Enterprise tactics. Solid cards come from the MITRE CTID KEV mappings; dashed cards are inferred by CVERadar from the CWE or description. Correct defences are real ATT&CK mitigations for that technique.
Pick a red technique card on the board, then choose the defence that stops it.
Defend against T1005 Data from Local System Inferred
Inferred from CWE CWE-200
How to fix it
Fixed versions
- dataease dataease: upgrade to 2.5.0 or later
Derived from the NVD CPE configuration (versionEndExcluding / versionEndIncluding). Always confirm with the vendor advisory.
Vendor advisories and patches
- https://github.com/dataease/dataease/releases/tag/v2.5.0 (Release Notes)
- https://github.com/dataease/dataease/security/advisories/GHSA-8gvx-4qvj-6vv5 (Vendor Advisory)
MITRE ATT&CK mitigations for this chain
- M1057 Data Loss Prevention (for T1005) : Data loss prevention can restrict access to sensitive data and detect sensitive data that is unencrypted.
Detection Generic guidance
- Collection: Watch for bulk reads of databases, file shares or mailboxes by the affected service.
Response checklist Generic guidance
- Inventory: find every instance of the affected product and version (include internet-facing and forgotten ones).
- Patch or mitigate per the vendor advisory; if you cannot patch, remove internet exposure or apply the vendor workaround.
- Assume compromise if the system was exposed before patching: hunt for the indicators in the advisory and review logs back to the disclosure date.
- Rotate credentials and secrets stored on or used by the affected system if compromise cannot be ruled out.