GHSA-c6px-4grw-hrjr: Binjs io 'Read' On Uninitialized Memory May Vulnerability

HIGH
Published
Advisory Summary

GHSA-c6px-4grw-hrjr is a HIGH 'read' on uninitialized memory may vulnerability (General Security Weakness) affecting Binjs io libraries in the crates.io ecosystem. The issue involves 'read' on uninitialized memory may cause ub. Remediation is available in the latest vendor maintenance releases.

GHSA-c6px-4grw-hrjr at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-c6px-4grw-hrjr
Severity HIGH
CVSS v3.1 Base Score N/A
CWE Classification General Security Weakness
Affected Product Binjs io
Package Ecosystem crates.io
Published Date
Last Updated

How to Fix GHSA-c6px-4grw-hrjr

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

binjs_io fixed: Latest secure release
Upgrade binjs_io 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 binjs_io

How to Check if You Are Affected

To determine whether your application is affected by GHSA-c6px-4grw-hrjr, inspect your project dependencies for Binjs io:

inspect dependencies for binjs_io

Analyze the terminal output to locate any version of Binjs io 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 General Security Weakness. In Binjs io, 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 this crate passes an uninitialized buffer to a user-provided `Read` implementation. The crate currently contains 4 occurrences of such cases. Arbitrary `Read` implementations can read from the uninitialized buffer (memory exposure) and also can return incorrect number of bytes written to the buffer. Reading from uninitialized memory produces undefined values that can quickly invoke undefined behavior.

GHSA-c6px-4grw-hrjr Affected Binjs io Versions

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

References

Frequently Asked Questions

What is GHSA-c6px-4grw-hrjr?
GHSA-c6px-4grw-hrjr is a security vulnerability in Binjs io involving 'Read' on uninitialized memory may cause UB under General Security Weakness.
Which Binjs io versions are affected?
Affected versions include releases prior to current release patches across affected packages: binjs_io.
What version fixes GHSA-c6px-4grw-hrjr?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
Is binjs_io affected?
Yes, binjs_io is affected in releases prior to Latest secure release. Upgrade your dependency to Latest secure release or later.
What CWE is associated with GHSA-c6px-4grw-hrjr?
GHSA-c6px-4grw-hrjr is classified under General Security Weakness.
How can I check crates.io dependencies for GHSA-c6px-4grw-hrjr?
Run the dependency tree command: 'inspect dependencies for binjs_io'. 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
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-c6px-4grw-hrjr",
  "modified" : "2023-06-13T16:28:06Z",
  "published" : "2022-06-16T23:42:49Z",
  "aliases" : [ ],
  "summary" : "'Read' on uninitialized memory may cause UB",
  "details" : "Affected versions of this crate passes an uninitialized buffer to a user-provided `Read` implementation. The crate currently contains 4 occurrences of such cases. Arbitrary `Read` implementations can read from the uninitialized buffer (memory exposure) and also can return incorrect number of bytes written to the buffer.\nReading from uninitialized memory produces undefined values that can quickly invoke undefined behavior.\n",
  "severity" : [ ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "crates.io",
      "name" : "binjs_io"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "last_affected" : "0.2.1"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/binast/binjs-ref/issues/460"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/binast/binjs-ref"
  }, {
    "type" : "WEB",
    "url" : "https://rustsec.org/advisories/RUSTSEC-2021-0085.html"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2022-06-16T23:42:49Z",
    "nvd_published_at" : null
  }
}