CVE-2023-32310

DataEase API interface has IDOR vulnerability

Affected versions: <= 1.18.6

Workarounds

It is recommended to upgrade the version to v1.18.7.

References

If you have any questions or comments about this advisory:

Open an issue in https://github.com/dataease/dataease
Email us at [email protected]

The api interface for DataEase delete dashboard and delete system messages is vulnerable to IDOR.

The interface to delete the dashboard:

1. Create two users: user1 and user2
2. User1 creates a dashboard named pan1
3. User2 creates a dashboard named pan2
4. Both user1 and user2 share their dashboards with the demo user
5. User1 wants to delete his dashboard. We hijack the request with burpsuite. The request will probably look like this: POST /api/share/removePanelShares/440efa7f-efd8-11ed-bec7-1144724bc08c HTTP/1.1. 440efa7f-efd8-11ed-bec7-1144724bc08c is the ID of pan1
6. We replace this ID with the ID of pan2 and continue the execution (i.e. we delete the shares of others)
7. Successfully remove the shared link
   

The interface to delete system messages:

1. Our request to delete a message is shown below
   
2. We can delete all messages by simply enumerating the message ID, regardless of whether the message belongs to the requester or not.
3. The interface for marking read messages is also affected

CVE-2023-32310 has a CVSS score of 8.1 (High). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.18.7); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

The vulnerability has been fixed in v1.18.7.

1. What is CVE-2023-32310? CVE-2023-32310 is a high-severity security vulnerability in io.dataease:dataease-plugin-common (maven), affecting versions <= 1.18.6. It is fixed in 1.18.7.
2. How severe is CVE-2023-32310? CVE-2023-32310 has a CVSS score of 8.1 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of io.dataease:dataease-plugin-common are affected by CVE-2023-32310? io.dataease:dataease-plugin-common (maven) versions <= 1.18.6 is affected.
4. Is there a fix for CVE-2023-32310? Yes. CVE-2023-32310 is fixed in 1.18.7. Upgrade to this version or later.
5. Is CVE-2023-32310 exploitable, and should I be worried? Whether CVE-2023-32310 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2023-32310 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2023-32310? Upgrade io.dataease:dataease-plugin-common to 1.18.7 or later.

Other vulnerabilities in io.dataease:dataease-plugin-common