CVE-2024-2435 Affecting temporal-fips package, versions <0.11.0-r4


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.04% (12th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-CHAINGUARDLATEST-TEMPORALFIPS-6669222
  • published19 Apr 2024
  • disclosed2 Apr 2024

Introduced: 2 Apr 2024

CVE-2024-2435  (opens in a new tab)

How to fix?

Upgrade Chainguard temporal-fips to version 0.11.0-r4 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream temporal-fips package and not the temporal-fips package as distributed by Chainguard. See How to fix? for Chainguard relevant fixed versions and status.

For an attacker with pre-existing access to send a signal to a workflow, the attacker can make the signal name a script that executes when a victim views that signal. The XSS is in the timeline page displaying the workflow execution details of the workflow that was sent the crafted signal. Access to send a signal to a workflow is determined by how you configured the authorizer on your server. This includes any entity with permission to directly call SignalWorkflowExecution or SignalWithStartWorkflowExecution, or any entity can deploy a worker that has access to call workflow progress APIs (specifically RespondWorkflowTaskCompleted).