GHSA-w48j-pp7j-fj55
CRITICALValtimo scripting engine can be used to gain access to sensitive data or resources
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Blast Radius
com.ritense.valtimo:core☕com.ritense.valtimo:coreReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
Impact
Any admin that can create or modify and execute process-definitions could gain access to sensitive data or resources.
This includes but is not limited to:
- Running executables on the application host
- Inspecting and extracting data from the host environment or application properties
- Spring beans (application context, database pooling)
Attack requirements
The following conditions have to be met in order to perform this attack:
- The user must be logged in
- The user must have the admin role (ROLE_ADMIN), which is required to change process definitions
- The user must have some knowledge about running scripts via a the Camunda/Operator engine
Patches
Version 12.16.0 and 13.1.2 have been patched. It is strongly advised to upgrade.
Workarounds
If no scripting is needed in any of the processes, it could be possible to disable it altogether via the ProcessEngineConfiguration:
@Component
class NoScriptEnginePlugin : ProcessEnginePlugin {
override fun preInit(processEngineConfiguration: ProcessEngineConfigurationImpl) {}
override fun postInit(processEngineConfiguration: ProcessEngineConfigurationImpl) {
processEngineConfiguration.scriptEngineResolver = null
}
override fun postProcessEngineBuild(processEngine: ProcessEngine) {}
}
Warning: this workaround could lead to unexpected side-effects. Please test thoroughly.
References
- Valtimo 12 and lower: Camunda Scripting
- Valtimo 13 and higher: Operaton Scripting
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | com.ritense.valtimo:core | all versions | 12.16.0.RELEASE |
| ☕Maven | com.ritense.valtimo:core | ≥ 13.0.0.RELEASE&&< 13.1.2.RELEASE | 13.1.2.RELEASE |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.ritense.valtimo:core. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update com.ritense.valtimo:core to 12.16.0.RELEASE or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-w48j-pp7j-fj55 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-w48j-pp7j-fj55 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-w48j-pp7j-fj55. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-w48j-pp7j-fj55 in your dependencies?
O3 detects GHSA-w48j-pp7j-fj55 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.