Headline
GHSA-7hv6-gv38-78wj: DataEase API interface has IDOR vulnerability
Impact
The api interface for DataEase delete dashboard and delete system messages is vulnerable to IDOR.
The interface to delete the dashboard:
- Create two users: user1 and user2
- User1 creates a dashboard named pan1
- User2 creates a dashboard named pan2
- Both user1 and user2 share their dashboards with the demo user
- 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
- We replace this ID with the ID of pan2 and continue the execution (i.e. we delete the shares of others)
- Successfully remove the shared link
The interface to delete system messages:
- Our request to delete a message is shown below
- We can delete all messages by simply enumerating the message ID, regardless of whether the message belongs to the requester or not.
- The interface for marking read messages is also affected
Affected versions: <= 1.18.6
Patches
The vulnerability has been fixed in v1.18.7.
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]
- GitHub Advisory Database
- GitHub Reviewed
- CVE-2023-32310
DataEase API interface has IDOR vulnerability
High severity GitHub Reviewed Published Jun 1, 2023 in dataease/dataease • Updated Jun 2, 2023
Package
maven io.dataease:dataease-plugin-common (Maven)
Affected versions
<= 1.18.6
Impact
The api interface for DataEase delete dashboard and delete system messages is vulnerable to IDOR.
The interface to delete the dashboard:
- Create two users: user1 and user2
- User1 creates a dashboard named pan1
- User2 creates a dashboard named pan2
- Both user1 and user2 share their dashboards with the demo user
- 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
- We replace this ID with the ID of pan2 and continue the execution (i.e. we delete the shares of others)
- Successfully remove the shared link
The interface to delete system messages:
Our request to delete a message is shown below
We can delete all messages by simply enumerating the message ID, regardless of whether the message belongs to the requester or not.
The interface for marking read messages is also affected
Affected versions: <= 1.18.6
Patches
The vulnerability has been fixed in v1.18.7.
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]
References
- GHSA-7hv6-gv38-78wj
- https://nvd.nist.gov/vuln/detail/CVE-2023-32310
- dataease/dataease#5342
- dataease/dataease@72f428e
- https://github.com/dataease/dataease/releases/tag/v1.18.7
Published to the GitHub Advisory Database
Jun 2, 2023
Related news
DataEase is an open source data visualization and analysis tool. The API interface for DataEase delete dashboard and delete system messages is vulnerable to insecure direct object references (IDOR). This could result in a user deleting another user's dashboard or messages or interfering with the interface for marking messages read. The vulnerability has been fixed in v1.18.7. There are no known workarounds aside from upgrading.