GHSA-mgg8-9pvp-6qcw: Noise search MvccRwLock Allows Data Races & Vulnerability

MODERATE
Share
CWE-362
Published
Advisory Summary

GHSA-mgg8-9pvp-6qcw is a MODERATE mvccrwlock allows data races & vulnerability (CWE-362: Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')) affecting Noise search libraries in the crates.io ecosystem. The issue involves mvccrwlock allows data races & aliasing violations. Remediation is available in the latest vendor maintenance releases.

GHSA-mgg8-9pvp-6qcw at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-mgg8-9pvp-6qcw
Severity MODERATE
CVSS v3.1 Base Score N/A
CWE Classification CWE-362: Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')
Affected Product Noise search
Package Ecosystem crates.io
Published Date
Last Updated

How to Fix GHSA-mgg8-9pvp-6qcw

To remediate this vulnerability, upgrade all affected Noise search dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

noise_search fixed: Latest secure release 
Upgrade noise_search to Latest secure release
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

inspect dependencies for noise_search

How to Check if You Are Affected

To determine whether your application is affected by GHSA-mgg8-9pvp-6qcw, inspect your project dependencies for Noise search:

inspect dependencies for noise_search

Analyze the terminal output to locate any version of Noise search in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-362: Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition'), where the product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently. In Noise search, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

Affected versions of the `noise_search` crate unconditionally implement Send/Sync for `MvccRwLock`. This can lead to data races when types that are either `!Send` or `!Sync` (e.g. `Rc<T>`, `Arc<Cell<_>>`) are contained inside `MvccRwLock` and sent across thread boundaries. The data races can potentially lead to memory corruption (as demonstrated in the PoC from the original report issue). Also, safe APIs of `MvccRwLock` allow aliasing violations by allowing `&T` and `LockResult<MutexGuard<Box<T>>>` to co-exist in conflicting lifetime regions. The APIs of `MvccRwLock` should either be marked as `unsafe` or `MbccRwLock` should be changed to private or pub(crate).

GHSA-mgg8-9pvp-6qcw Affected Noise search Versions

1 component(s)
Product / Package Ecosystem Affected Versions Fixed Version
noise_search
 crates.io
≤ 0.7.0

References

Noise search Source Repository REPOSITORY
https://github.com/pipedown/noise/issues/72
Noise search Source Repository REPOSITORY
https://github.com/pipedown/noise
rustsec.org/advisories/rustsec-... WEB
https://rustsec.org/advisories/RUSTSEC-2020-0141.html

Frequently Asked Questions

What is GHSA-mgg8-9pvp-6qcw?
GHSA-mgg8-9pvp-6qcw is a security vulnerability in Noise search involving MvccRwLock allows data races & aliasing violations under CWE-362: Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition').
Which Noise search versions are affected?
Affected versions include releases prior to current release patches across affected packages: noise_search.
What version fixes GHSA-mgg8-9pvp-6qcw?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
Is noise_search affected?
Yes, noise_search is affected in releases prior to Latest secure release. Upgrade your dependency to Latest secure release or later.
What CWE is associated with GHSA-mgg8-9pvp-6qcw?
GHSA-mgg8-9pvp-6qcw is classified under CWE-362: Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') (The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.).
How can I check crates.io dependencies for GHSA-mgg8-9pvp-6qcw?
Run the dependency tree command: 'inspect dependencies for noise_search'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-mgg8-9pvp-6qcw",
  "modified" : "2021-08-24T18:01:27Z",
  "published" : "2021-08-25T20:59:59Z",
  "withdrawn" : "2021-08-24T18:01:27Z",
  "aliases" : [ ],
  "summary" : "MvccRwLock allows data races & aliasing violations",
  "details" : "Affected versions of the `noise_search` crate unconditionally implement Send/Sync for `MvccRwLock`.\nThis can lead to data races when types that are either `!Send` or `!Sync` (e.g. `Rc<T>`, `Arc<Cell<_>>`) are contained inside `MvccRwLock` and sent across thread boundaries. The data races can potentially lead to memory corruption (as demonstrated in the PoC from the original report issue).\n\nAlso, safe APIs of `MvccRwLock` allow aliasing violations by allowing `&T` and `LockResult<MutexGuard<Box<T>>>` to co-exist in conflicting lifetime regions. The APIs of `MvccRwLock` should either be marked as `unsafe` or `MbccRwLock` should be changed to private or pub(crate).\n",
  "severity" : [ ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "crates.io",
      "name" : "noise_search"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "last_affected" : "0.7.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/pipedown/noise/issues/72"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/pipedown/noise"
  }, {
    "type" : "WEB",
    "url" : "https://rustsec.org/advisories/RUSTSEC-2020-0141.html"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-362" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2021-08-09T17:16:18Z",
    "nvd_published_at" : null
  }
}