ConqueueApplication · Conqueue Project
CVE-2020-36437
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 conqueue crate before 0.4.0 for Rust. There are unconditional implementations of Send and Sync for QueueSender<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 conqueue crate before 0.4.0 unconditionally implements Send and Sync traits for QueueSender<T> regardless of whether T is thread-safe. This is a soundness vulnerability because it incorrectly marks QueueSender as thread-safe even when T contains non-Send/Sync types like Rc<T>, potentially allowing data races and undefined behavior when non-thread-safe data is moved across threads.
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
ConqueueApplication
< 0.4.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.
-
Identify conqueue dependency in projectSearch Cargo.toml files for 'conqueue' under [dependencies] or [dev-dependencies] and note the version specifiedAffected if conqueue is listed with a version constraint lower than 0.4.0 (e.g., '0.3', '0.2', or any wildcard like '*')
-
Check Cargo.lock for exact conqueue versionOpen Cargo.lock and locate the [[package]] entry for name 'conqueue' to find the resolved version numberAffected if The version field shows anything before 0.4.0 (e.g., 0.3.0, 0.3.1)
-
Inspect QueueSender usage for non-Send/Sync typesSearch source code for QueueSender<T> instantiations and examine the type T being passed. Look for non-Send/Sync types such as Rc<T>, Cell<T>, RefCell<T>,RcCell<T>, or custom types not implementing Send or SyncAffected if QueueSender is instantiated with a type T that does not implement Send or Sync traits
-
Check for cross-thread QueueSender movementSearch code for patterns where QueueSender is moved between threads (e.g., spawned threads, thread::spawn closures capturing QueueSender, or passing QueueSender to cross-thread channels/APIs)Affected if QueueSender instances are moved across thread boundaries in code
The environment is affected if conqueue version is below 0.4.0 AND QueueSender<T> is used with types that do not implement Send/Sync AND those QueueSender instances are moved 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.4.0
Upgrade conqueue to version 0.4.0 or later which implements Send and Sync conditionally based on the thread-safety of T. If upgrading is not possible, avoid using QueueSender with non-Send/Sync types.
0.4.0
- Check your Cargo.toml for the current conqueue dependency version
- Update the conqueue version requirement to 0.4.0 or later (e.g., conqueue = "0.4.0")
- Run `cargo update conqueue` or `cargo build` to fetch the fixed version
- Verify the update was successful by checking the resolved version
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Conqueue
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-36437 — 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-36437 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