CVE-2024-34706: @valtimo/components exposes access token to form.io

Should you act?

Critical and remotely reachable

No known exploitation yet, but it is network-reachable without credentials. This signal is computed from CISA KEV, EPSS and CVSS data; it is not an editorial verdict.

• No confirmed exploitation. It is not in CISA’s KEV catalog and CISA’s SSVC assessment records no known exploitation. That can change quickly after a public write-up; re-check if you are affected.
• EPSS 1.1%, percentile 64: FIRST’s model estimates a 1.1% chance of exploitation activity in the next 30 days, higher than 64% of all scored CVEs (moderate). EPSS is a probability, not a verdict.
• Remotely reachable with no login and no user interaction. If the vulnerable service is exposed to the internet, prioritize it.
• Only applies if your dependency tree includes @valtimo/components (npm) < 10.8.4, fixed in 10.8.4; @valtimo/components (npm) >= 11.0.0, < 11.1.6, fixed in 11.1.6; @valtimo/components (npm) >= 11.2.0, < 11.2.2, fixed in 11.2.2. Check your lockfile, including transitive dependencies.

What it is

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.

From the GitHub advisory

Impact 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.

Attack requirements ### 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. - An attacker needs to act within the time-to-live of the access token. The default TTL in Keycloak is 5 minutes.

Patches Versions 10.8.4, 11.1.6 and 11.2.2 have been patched

Weakness type: CWE-532.

Product: @valtimo/components (npm) · Assigned by: GitHub_M · Published: 2024-05-13

Affected and fixed versions

Severity scores

• Attack vector: network (remotely reachable)
• Attack complexity: low
• Privileges required: none (no login)
• User interaction: none
• Scope: unchanged

CVSS measures how bad a flaw is if exploited, not how likely exploitation is. Read it next to the exploitation data below.

Exploitation and urgency

• CISA KEV: not listed (no confirmed in-the-wild exploitation known to CISA).
• CISA SSVC assessment: exploitation none, automatable yes, technical impact total.
• FIRST EPSS (model of 2026-10-21): 1.06% probability of exploitation activity in the next 30 days; percentile 64.

Timeline

• 2024-05-13 — CVE record published by GitHub_M
• 2024-05-13 — GitHub-reviewed advisory GHSA-xcp4-62vj-cq3r published (critical)
• 2024-08-02 — CVE record last updated

Sources and references

Original sources first. Version and fix details should always be confirmed against the vendor or project advisory.

Vulnerability records

1. GitHub Advisory GHSA-xcp4-62vj-cq3r github.com
2. CVE.org record CVE-2024-34706 cve.org
3. NVD entry CVE-2024-34706 nvd.nist.gov

Other references from the CVE record and advisory

1. github.com github.com
2. github.com github.com
3. github.com github.com
4. github.com github.com

Critical npm advisories · Today’s Security Digest