Paper/Archive/CVE-2021-39228

CVE-2021-39228

tremor-rs tremor-runtime — Memory Safety Issue when using patch or merge on state and assign the result back to state

Description · from the CVE record

Tremor is an event processing system for unstructured data. A vulnerability exists between versions 0.7.2 and 0.11.6. This vulnerability is a memory safety Issue when using `patch` or `merge` on `state` and assign the result back to `state`. In this case, affected versions of Tremor and the tremor-script crate maintains references to memory that might have been freed already. And these memory regions can be accessed by retrieving the `state`, e.g. send it over TCP or HTTP. This requires the Tremor server (or any other program using tremor-script) to execute a tremor-script script that uses the mentioned language construct. The issue has been patched in version 0.11.6 by removing the optimization and always cloning the target expression of a Merge or Patch. If an upgrade is not possible, a possible workaround is to avoid the optimization by introducing a temporary variable and not immediately reassigning to `state`.

Affected

ProductAffectedFixed inSource
tremor-runtime> 0.7.2, < 0.11.6–CNA

Scores by source

NVD9.8CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
GitHub_M (CNA)6.5CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

References

refgithub.com/tremor-rs/tremor-runtime/security/advisories/GHSA-mc22-5q92-8v85refgithub.com/tremor-rs/tremor-runtime/pull/1217refgithub.com/tremor-rs/tremor-runtime/commit/1a2efcdbe68e5e7fd0a05836ac32d2cde78a0b2erefgithub.com/tremor-rs/tremor-runtime/releases/tag/v0.11.6