CVE-2022-39312
What it is
Dataease is an open source data visualization analysis tool. Dataease prior to 1.15.2 has a deserialization vulnerability. In Dataease, the Mysql data source in the data source function can customize the JDBC connection parameters and the Mysql server target to be connected. In `backend/src/main/java/io/dataease/provider/datasource/JdbcProvider.java`, the `MysqlConfiguration` class does not filter any parameters. If an attacker adds some parameters to a JDBC url and connects to a malicious mysql server, the attacker can trigger the mysql jdbc deserialization vulnerability. Through the deserialization vulnerability, the attacker can execute system commands and obtain server privileges. Version 1.15.2 contains a patch for this issue.
At a glance
- Exploitability
- Can be exploited over the network without logging in. High risk of data exposure, data tampering, service disruption.
- Exploit odds
- 1.9% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 1.9% in the next 30 days (EPSS).
- Severity: 9.8 CRITICAL (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 1.9% · EPSS, next 30 days
- Weakness
- CWE-20 · Improper input validation
- Record status
- Modified
Affected
- Dataease < 1.15.2
Attack profile CVSS 3.1 · 9.8
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2022-39312.md and follow it. Check whether this project is affected by CVE-2022-39312. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://github.com/dataease/dataease/commit/956ee2d6c9e81349a60aef435efc046888e10a6d
- https://github.com/dataease/dataease/pull/3328
- https://github.com/dataease/dataease/releases/tag/v1.15.2
- https://github.com/dataease/dataease/security/advisories/GHSA-q4qq-jhjv-7rh2
- https://github.com/dataease/dataease/commit/956ee2d6c9e81349a60aef435efc046888e10a6d
- https://github.com/dataease/dataease/pull/3328
- https://github.com/dataease/dataease/releases/tag/v1.15.2
- https://github.com/dataease/dataease/security/advisories/GHSA-q4qq-jhjv-7rh2
References
- https://github.com/dataease/dataease/commit/956ee2d6c9e81349a60aef435efc046888e10a6d
- https://github.com/dataease/dataease/pull/3328
- https://github.com/dataease/dataease/releases/tag/v1.15.2
- https://github.com/dataease/dataease/security/advisories/GHSA-q4qq-jhjv-7rh2
- https://github.com/dataease/dataease/commit/956ee2d6c9e81349a60aef435efc046888e10a6d
- https://github.com/dataease/dataease/pull/3328
- https://github.com/dataease/dataease/releases/tag/v1.15.2
- https://github.com/dataease/dataease/security/advisories/GHSA-q4qq-jhjv-7rh2