Ticketed LockApplication · Ticketed Lock Project
CVE-2020-36439
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 ticketed_lock crate before 0.3.0 for Rust. There are unconditional implementations of Send for ReadTicket<T> and WriteTicket<T>.
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 · high confidenceThe ticketed_lock crate before 0.3.0 unconditionally implements the `Send` trait for `ReadTicket<T>` and `WriteTicket<T>` types. This allows these lock tickets to be transferred across threads even when the contained data type T is not thread-safe (does not implement `Sync`), potentially leading to data races and undefined behavior.
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
Ticketed LockApplication
< 0.3.0CVSS 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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/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.
-
Locate ticketed_lock in your dependency treeSearch your Cargo.toml for 'ticketed_lock' under [dependencies] and check Cargo.lock for the resolved versionAffected if The crate is present with a version lower than 0.3.0 (e.g., 0.2.x, 0.1.x)
-
Identify ReadTicket and WriteTicket usageGrep your source code for 'ReadTicket<' and 'WriteTicket<' type instantiationsAffected if Either type is instantiated with a concrete type parameter T
-
Verify if the contained type is Sync-safeFor each ReadTicket<T> or WriteTicket<T> found, check if T implements the Sync trait (consult your code or check the type's documentation)Affected if T does not implement Sync (for example, using Rc<T>, RefCell<T>, or custom types without Send+Sync bounds)
-
Check for cross-thread ownership transferSearch for code that moves ReadTicket<T> or WriteTicket<T> across thread boundaries (e.g., passing to thread::spawn, sending through channels)Affected if These types are transferred to another thread while containing a non-Sync type T
You are affected if ticketed_lock version < 0.3.0 is in your dependencies AND you use ReadTicket<T> or WriteTicket<T> with a type T that does not implement Sync and that gets transferred across threads.
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.3.0
Upgrade to ticketed_lock version 0.3.0 or later, which presumably introduces conditional Send implementations based on the thread-safety of T.
0.3.0
- Update the version specification in Cargo.toml to require ticketed_lock version 0.3.0 or later (e.g., ticketed_lock = "0.3.0")
- Run `cargo update ticketed_lock` to fetch the new version
- Run `cargo build` or `cargo check` to verify the update compiles successfully
- Verify no runtime issues arise from the Send trait bound changes
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Ticketed Lock
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-36439 — 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-2020-36439 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