Tremor ScriptApplication · Linuxfoundation
CVE-2021-45702
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn issue was discovered in the tremor-script crate before 0.11.6 for Rust. A merge operation may result in a use-after-free.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA use-after-free vulnerability exists in the tremor-script Rust crate's merge operation in versions prior to 0.11.6. The merge logic incorrectly frees memory that is still being referenced, allowing an attacker to potentially access freed memory.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Tremor ScriptApplication
>= 0.7.2, < 0.11.6CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify tremor-script installationSearch for tremor-script in your project's Cargo.lock file, package manifests, or installed binaries. If using Tremor (the event processing system), check its dependencies for tremor-script.Affected if tremor-script is present as a dependency or embedded component
-
Determine installed tremor-script versionRun `cargo tree -p tremor-script` to see the exact version, or check Cargo.lock for the tremor-script entry. If using a Tremor binary, check its version with `--version`.Affected if The version is 0.7.2 or higher but lower than 0.11.6
-
Verify merge operation is in useReview your tremor-script scripts or configurations for use of the `merge` keyword or merge operation, as this is the vulnerable code path.Affected if The merge operation is actively used in your tremor-script configurations
You are affected if tremor-script version is >= 0.7.2 and < 0.11.6, AND the merge operation is being executed in your scripts.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped0.11.6
Upgrade the tremor-script crate to version 0.11.6 or later to obtain the patched version.
0.11.6
- Update the tremor-script dependency in your Cargo.toml to version 0.11.6 or later: change `tremor-script = "0.11.x"` to `tremor-script = "0.11.6"` or use a newer version specification like `tremor-script = "0.11"`
- Run `cargo update tremor-script` or `cargo build` to fetch the fixed version
- Test your application to verify the upgrade resolves the use-after-free vulnerability and does not introduce regressions
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Tremor Script
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-45702 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-45702 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data