Description
DataEase before 2.10.26 contains multiple access control defects in the sharing link module. Tickets are not bound to the target share UUID, so a valid ticket issued for one share can be reused against another (ShareTicketManage.validateTicket / POST /de2api/share/proxyInfo). The POST /de2api/share/validate endpoint issues a LinkToken after password verification without requiring a ticket, bypassing the 'ticket mandatory' policy. Additionally, the ticket create and delete endpoints (POST /de2api/ticket/saveTicket, POST /de2api/ticket/delTicket) lack share-ownership checks, allowing an authenticated user who knows another user's ticket to modify, rebind, or delete it (denial of service), and GET /de2api/share/queryRelationByUserId/{uid} allows authenticated users to enumerate other users' share mappings.
Affected products
Version statuses are supplied by the assigning organization. Consult the original record for detailed ranges and platform conditions.
dataease dataease
Default version status: unaffected
0 to < 2.10.26affected2.10.26unaffected
pkg:github/dataease/dataeaseReferences
- https://github.com/dataease/dataease/security/advisories/GHSA-9h54-39gh-5qfg ↗
- https://github.com/dataease/dataease/commit/fbbb0482c4c10480c2dd4ecc050cd1e5c55b17db ↗
- https://github.com/dataease/dataease/releases/tag/v2.10.26 ↗
- https://github.com/dataease/dataease ↗
- https://www.vulncheck.com/advisories/dataease-before-2.10.26-access-control-bypass-via-share-tickets ↗