CVE-2025-64428
BaseFortify
Publication date: 2025-11-20
Last updated on: 2025-11-24
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| dataease | dataease | to 2.10.17 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-74 | The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a JNDI injection in Dataease, an open source data visualization tool. Versions before 2.10.17 are affected. Although a blacklist was introduced in version 2.10.14 to block some injection attempts, the vulnerability still exists through certain schemes like iiop, corbaname, and iiopname. It allows attackers to inject malicious JNDI lookups, potentially leading to remote code execution or other severe impacts. The issue was fixed in version 2.10.17.
How can this vulnerability impact me? :
This vulnerability can have a high impact as it allows remote attackers to perform JNDI injection, which can lead to remote code execution or other severe security breaches without any user interaction or privileges required. This can compromise the confidentiality, integrity, and availability of the affected system and data.
What immediate steps should I take to mitigate this vulnerability?
Upgrade Dataease to version 2.10.17 or later, as this version contains the fix for the JNDI injection vulnerability. Avoid using versions prior to 2.10.17, especially those before 2.10.14 which only partially address the issue. Additionally, be aware that the blacklist added in version 2.10.14 does not fully prevent JNDI injection via iiop, corbaname, and iiopname schemes.