llamaCVEVulnerability Intelligence
/
Advisory · GitHub · Maven · io.dataease

GHSA-494P-38Q6-9GX5

Missing authorization checks in DataEase geographic information, linkage and chart APIs

Texto original en inglés · Ver en español

Parche disponible
Descargar PNG JSON
CVSS
—
high
Fuente: —
ExplotaciónSin evidenciaNo figura en CISA KEV
Exploits públicos0Ninguno conocido
Parche1 versión2.10.26
Exposición114 dDesde la divulgación, 30 jul 2026, 2:55 a. m.
Detección111 dDesde la divulgación hasta su ingreso al índice
Decisión estimadaSeguir
Remediar en la ventana regular de mantenimiento
Estimación de Llama con el árbol SSVC de CISA a partir de la severidad declarada por GHSA (alta) y la evidencia de explotación (sin evaluación oficial): sin explotación conocida, no automatizable e impacto técnico parcial. Hay versiones corregidas disponibles.
Si sale un exploit, la subo de categoría. Atento.Como dice el refrán: más vale prevenir que restaurar backups.
Timeline

Ciclo de vida de la vulnerabilidad

Hoy
Divulgación
Publicada
Explotación
Remediación
Monitoreo
Detectada +1
30 jul 26
18 nov 26
21 nov 26
30 jul 26
27 ago 26
25 sept 26
24 oct 26
21 nov 26
FechaFaseEventoDetalle
Divulgación Publicada GHSA-494P-38Q6-9GX5 divulgada
Monitoreo Detectada Ingresó al índice
Monitoreo Verificada Última verificación contra las fuentes
Resumen
Descripción del advisory
Texto original · GitHub · en inglés
Impact

#### Issue 1: Missing Backend Authorization for Geographic Information Interfaces
Affected endpoints:
- POST /de2api/geometry/save
- POST /de2api/geometry/delete/{id}
- POST /de2api/geometry/{id}/mapping

##### Description
These endpoints lack explicit @DePermit annotation or equivalent ownership validation logic. The implementation directly persists, deletes or modifies global geographic information and GeoJSON files.

##### Impact
An authenticated logged-in user can modify or delete global map resources.
This may lead to broken map rendering, unavailable map assets or tampered geographic name mappings, impacting other users and dashboards that consume these map resources.
No capability to directly access business databases or execute system commands has been identified. The risk is limited to the integrity of map assets.

#### Issue 2: Missing Dashboard Ownership Validation for Linkage Write Interfaces
Affected endpoints:
- POST /de2api/linkage/saveLinkage
- POST /de2api/linkage/updateLinkageActive
- POST /de2api/linkage/removeLinkage

##### Description
These write endpoints perform database create/update/delete operations directly using dvId, sourceViewId and target view IDs supplied in the request. There is no validation to verify whether the current user holds management permissions for the corresponding dashboard.
Read-related linkage endpoints utilise @DeLinkPermit, but consistent permission checks have not been implemented for write operations.

##### Impact
If an authenticated user obtains another user’s dashboard ID, they may alter or remove linkage configurations.
Consequences include broken chart filters, inactive linkage or tampered linkage logic.
The vulnerability primarily affects dashboard configuration integrity and generally does not lead to direct exposure of business data.

#### Issue 3: Incomplete Object-Level Authorization for Chart ID-Based Access
Affected endpoints:
- POST /de2api/chart/getChart/{id}
- POST /de2api/chart/listByDQ/{id}/{chartId}

##### Description
These endpoints query data based on chart IDs, dataset IDs or field IDs provided in requests. No object-level permission checks matching dashboard or chart ownership are present in the endpoint definitions.
Verification confirms that supplying a known chart ID returns chart metadata, field configurations and calculation results. While some endpoints implement column-level filtering or data masking, this is not equivalent to verifying whether the requesting user is authorised to access the chart object itself.
Note:
POST /de2api/chartData/getData implements the @DeLinkPermit annotation. Not all chart data retrieval endpoints are vulnerable; each API must be evaluated individually against its permission logic.

##### Impact
An authenticated user who obtains another user’s chart ID can retrieve chart metadata. Certain call chains may additionally expose chart calculation outputs.
Sensitive information including chart configurations, dataset associations, fields and filter rules may be disclosed.
In multi-tenant or multi-project deployments, this can result in cross-user / cross-project information leakage.
Combined Impact
All identified issues require a valid authenticated session; unauthenticated exploitation has not been confirmed.
Successful exploitation may lead to:
- Tampering of global geographic map resources;
- Unauthorised modification or deletion of linkage rules belonging to other users’ dashboards;
- Horizontal privilege escalation to read chart metadata and partial calculation results 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.

Versiones

Rangos afectados

Afectada Corregida
io.dataease< 2.10.26
2.10.26
Remediación

Estado del parche por paquete

Paquete / productoEstadoCorregida enDesde divulgaciónÚltima versión
Mavenio.dataease
Corregida 2.10.26 — —
Versiones corregidas2.10.26
Explotación

Arsenal público

Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.

Referencias
Advisoryhttps://github.com/dataease/dataease/security/advisories/GHSA-494p-38q6-9gx5

Las referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.