GHSA-9H54-39GH-5QFG
Access Control Vulnerabilities in the Sharing Link Module of DataEase
Texto original en inglés · Ver en español
Ciclo de vida de la vulnerabilidad
| Fecha | Fase | Evento | Detalle |
|---|---|---|---|
| Divulgación | Publicada | GHSA-9H54-39GH-5QFG divulgada | |
| Monitoreo | Detectada | Ingresó al índice | |
| Monitoreo | Verificada | Última verificación contra las fuentes |
### Impact
#### Issue A: Share tickets are not bound and validated against the target share UUID
##### Relevant component & endpoint:
- ShareTicketManage.validateTicket
- POST /de2api/share/proxyInfo
The ticket validation logic looks up records purely by the ticket string, without verifying that the ticket’s associated share UUID matches the share UUID being accessed in the request.
##### Proof of concept
A valid ticket originally issued for Share A can be submitted against Share B. If the password for Share B is verified successfully, /share/proxyInfo will return a valid X-DE-LINK-TOKEN.
##### Potential Impact
- Tickets are reusable across different shares.
- A ticket belonging to Share A may be abused to access Share B.
- If tickets are leaked via URLs, emails, logs or browser history, the attack surface for other published shares expands.
#### Issue B: /share/validate issues LinkToken without requiring a ticket after successful password verification
##### Affected endpoint
- POST /de2api/share/validate
After successfully verifying the share UUID and password, this endpoint generates and returns a LinkToken without requiring or validating a ticket.
##### Practical verification
Even when the target share has ticketRequire=true, supplying only the correct share UUID and password (with no ticket) will still return a valid X-DE-LINK-TOKEN.
##### Potential Impact
- The "ticket mandatory" sharing policy can be bypassed.
- An actor who obtains the share UUID and password can obtain a LinkToken without a ticket.
- This behaviour is inconsistent with /share/proxyInfo, which enforces simultaneous checks for password, ticket and expiry.
#### Issue C: Missing share ownership checks on ticket create and delete endpoints
##### Affected endpoints
- POST /de2api/ticket/saveTicket
- POST /de2api/ticket/delTicket
##### Implementation details
- saveTicket: Performs lookups and updates based primarily on the ticket string.
- deleteTicket: Removes records directly based on the ticket string.
Neither endpoint implements explicit validation confirming whether the current user is the creator or administrator of the associated share.
##### Proof of concept
An authenticated logged-in user who learns another user’s share ticket can:
- Modify the ticket’s bound share UUID
- Alter ticket configuration parameters
- Adjust ticket expiry time
- Permanently delete the target ticket
##### Potential Impact
- Third-party share tickets may be deleted, breaking public share access (denial of service).
- Tickets can be reconfigured and rebound to unrelated shares.
- This flaw may be chained with the cross-share ticket reuse vulnerability (Issue A) to escalate risk.
#### Issue D: queryRelationByUserId allows enumeration of other users’ share mappings
##### Affected endpoint
- GET /de2api/share/queryRelationByUserId/{uid}
The endpoint directly uses the uid path parameter to query share relationships. There is no restriction limiting queries to the requesting user’s own ID, nor any administrator privilege guard.
##### Practical verification
Authenticated users can query share mappings belonging to other users and retrieve the mapping between resourceId and share UUID.
##### Potential Impact
- Disclosure of share identifiers created by other platform users.
- Provides auxiliary information to attackers for share link enumeration and further access control testing.
- When chained with the ticket validation weaknesses above, lowers the barrier for attackers to locate target shares.
#### Combined Impact Summary
All four issues require a valid authenticated user session for exploitation; unauthenticated attack vectors have not been identified.
If confirmed as security vulnerabilities, successful exploitation may lead to:
- Cross-share reuse of access tickets;
- Bypass of mandatory-ticket share access policies;
- Unauthorised modification and deletion of other users’ share tickets;
- Enumeration of share resources owned by other users.
Affected versions
Affected versions < v2.10.26
Patches
The vulnerability has been fixed in v2.10.26.
Workarounds
It is recommended to upgrade the version to v2.10.26.
References
If you have any questions or comments about this advisory:
- Open an issue in https://github.com/dataease/dataease
- Email us at wei@fit2cloud.com
Incluye detalles técnicos publicados por el investigador. Úselos solo para validar y corregir sus propios sistemas.
Rangos afectados
Estado del parche por paquete
| Paquete / producto | Estado | Corregida en | Desde divulgación | Última versión |
|---|---|---|---|---|
Mavenio.dataease |
Corregida | 2.10.26 | — | — |
2.10.26Arsenal público
Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.
https://github.com/dataease/dataease/security/advisories/GHSA-9h54-39gh-5qfgLas referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.
