CVE-2024-30269
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedDataEase, 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceDataEase versions before 2.5.0 have an unauthenticated information disclosure vulnerability at the /de2api/engine/getEngine;.js endpoint. Visiting this path in a browser returns the platform's database configuration information, including potentially sensitive credentials and connection details.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 2.5.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm DataEase is running and accessibleCheck if the DataEase web interface is reachable by accessing the application's base URL (commonly on port 8080) in a browser or via curlAffected if DataEase is accessible over the network
-
Check the installed DataEase versionAccess the DataEase admin interface or API to identify the running version. This is typically visible in the UI footer, or accessible via an API endpoint like /api/sysInfo or through the system settings panelAffected if The installed version is lower than 2.5.0 (e.g., 2.0.x, 2.1.x, 2.2.x, 2.3.x, 2.4.x)
-
Test the vulnerable endpoint for exposureSend a GET request to http://<host>:<port>/de2api/engine/getEngine;.js (note the semicolon before .js) using a browser or curl commandAffected if The endpoint responds with HTTP 200 and returns JSON content containing database configuration details such as host, port, username, password, or connection strings
-
Verify if sensitive credentials are disclosedExamine the response from the /de2api/engine/getEngine;.js endpoint. Look for fields that may contain passwords, connection strings, or other sensitive database credentials in plain textAffected if The response contains unencrypted passwords, API keys, or connection credentials for the underlying database
A DataEase installation is affected if it is version 2.5.0 or earlier and the /de2api/engine/getEngine;.js endpoint returns database configuration with sensitive credentials without authentication.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped2.5.0
Upgrade to DataEase v2.5.0 or later. No workarounds are available; the vendor recommends upgrading as the only remediation path.
2.5.0
- Upgrade Dataease to version 2.5.0 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-30269 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-30269 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data