Valtimo is an open source business process and case management platform. When opening a form in Valtimo, the access token (JWT) of the user is exposed to `api.form.io` via the the `x-jwt-token` header. An attacker can retrieve personal information from this token, or use it to execute requests to the Valtimo REST API on behalf of the logged-in user. This issue is caused by a misconfiguration of the Form.io component. The following conditions have to be met in order to perform this attack: An attacker needs to have access to the network traffic on the `api.form.io` domain; the content of the `x-jwt-token` header is logged or otherwise available to the attacker; an attacker needs to have network access to the Valtimo API; and an attacker needs to act within the time-to-live of the access token. The default TTL in Keycloak is 5 minutes. Versions 10.8.4, 11.1.6 and 11.2.2 have been patched.
When opening a form in the Valtimo application, the frontend library incorrectly appends the user's JWT token (header `x-jwt-token`) to requests directed to the external domain `api.form.io`. This token should not leave trusted infrastructure. An attacker must have access to network traffic on that domain or logs containing the header value, and then possess network access to the Valtimo API. The attack must be conducted within the token validity window — the default TTL in Keycloak is 5 minutes.
An attacker can read personal data contained in the JWT token and perform unauthorized requests to Valtimo REST API with the privileges of the compromised user, which may lead to breaches of confidentiality, integrity, and data availability.
Update Valtimo frontend libraries to version 10.8.4, 11.1.6, or 11.2.2, which fix the incorrect Form.io component configuration. Details available in vendor references (GitHub Security Advisory GHSA-xcp4-62vj-cq3r).
Valtimo (valtimo-frontend-libraries) — versions prior to 10.8.4, 11.1.6, and 11.2.2
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H