GHSA-4v52-7q2x-v4xj: eyre Parts Of Report Are Dropped Vulnerability

HIGH
Share
CVSS 7.5
CWE-843
Published
Advisory Summary

GHSA-4v52-7q2x-v4xj is a HIGH (CVSS 7.5) parts of report are dropped vulnerability (CWE-843: Access of Resource Using Incompatible Type ('Type Confusion')) affecting eyre libraries in the crates.io ecosystem. The issue involves parts of report are dropped as the wrong type during downcast. Remediation is available by upgrading affected packages to version 0.6.12.

GHSA-4v52-7q2x-v4xj at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-4v52-7q2x-v4xj
Severity HIGH
CVSS v3.1 Base Score 7.5
CWE Classification CWE-843: Access of Resource Using Incompatible Type ('Type Confusion')
Affected Product eyre
Package Ecosystem crates.io
Published Date
Last Updated

Security Impact

CVSS: 7.5

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality None (C:N)
Integrity None (I:N)
Availability High (A:H)

How to Fix GHSA-4v52-7q2x-v4xj

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

eyre fixed: 0.6.12 
Upgrade eyre to 0.6.12
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 eyre

How to Check if You Are Affected

To determine whether your application is affected by GHSA-4v52-7q2x-v4xj, inspect your project dependencies for eyre:

inspect dependencies for eyre

Analyze the terminal output to locate any version of eyre in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.6.12), 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-843: Access of Resource Using Incompatible Type ('Type Confusion'), where the product allocates or initializes a resource such as a pointer, object, or variable using one type, but it later accesses that resource using a type that is incompatible with the original type. In eyre, 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

In affected versions, after a `Report` is constructed using `wrap_err` or `wrap_err_with` to attach a message of type `D` onto an error of type `E`, then using `downcast` to recover ownership of either the value of type `D` or the value of type `E`, one of two things can go wrong: - If downcasting to `E`, there remains a value of type `D` to be dropped. It is incorrectly "dropped" by running `E`'s drop behavior, rather than `D`'s. For example if `D` is `&str` and `E` is `std::io::Error`, there would be a call of `std::io::Error::drop` in which the reference received by the `Drop` impl does not refer to a valid value of type `std::io::Error`, but instead to `&str`. - If downcasting to `D`, there remains a value of type `E` to be dropped. When `D` and `E` do not happen to be the same size, `E`'s drop behavior is incorrectly executed in the wrong location. The reference received by the `Drop` impl may point left or right of the real `E` value that is meant to be getting dropped. In both cases, when the `Report` contains an error `E` that has nontrivial drop behavior, the most likely outcome is memory corruption. When the `Report` contains an error `E` that has trivial drop behavior (for example a `Utf8Error`) but where `D` has nontrivial drop behavior (such as `String`), the most likely outcome is that downcasting to `E` would leak `D`.

GHSA-4v52-7q2x-v4xj Affected eyre Versions

1 component(s)
Fixed Versions:
0.6.12
Product / Package Ecosystem Affected Versions Fixed Version
eyre
 crates.io
≥ 0.6.9
< 0.6.12
0.6.12

References

eyre Source Repository REPOSITORY
https://github.com/eyre-rs/eyre/issues/141
Security Fix Commit FIX COMMIT
https://github.com/eyre-rs/eyre/commit/770ac3fa1435eae3b166a4b072053360e38a0575
eyre Source Repository REPOSITORY
https://github.com/eyre-rs/eyre
rustsec.org/advisories/rustsec-... WEB
https://rustsec.org/advisories/RUSTSEC-2024-0021.html

Frequently Asked Questions

What is GHSA-4v52-7q2x-v4xj?
GHSA-4v52-7q2x-v4xj is a security vulnerability in eyre involving Parts of Report are dropped as the wrong type during downcast under CWE-843: Access of Resource Using Incompatible Type ('Type Confusion').
Which eyre versions are affected?
Affected versions include releases prior to 0.6.12 across affected packages: eyre.
What version fixes GHSA-4v52-7q2x-v4xj?
Upgrading to 0.6.12 (or the latest patched release for your respective branch) resolves the vulnerability.
Is eyre affected?
Yes, eyre is affected in releases prior to 0.6.12. Upgrade your dependency to 0.6.12 or later.
What is the CVSS score of GHSA-4v52-7q2x-v4xj?
GHSA-4v52-7q2x-v4xj has a CVSS v3.1 base score of 7.5 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H.
What CWE is associated with GHSA-4v52-7q2x-v4xj?
GHSA-4v52-7q2x-v4xj is classified under CWE-843: Access of Resource Using Incompatible Type ('Type Confusion') (The product allocates or initializes a resource such as a pointer, object, or variable using one type, but it later accesses that resource using a type that is incompatible with the original type.).
How can I check crates.io dependencies for GHSA-4v52-7q2x-v4xj?
Run the dependency tree command: 'inspect dependencies for eyre'. 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-4v52-7q2x-v4xj",
  "modified" : "2024-04-05T15:08:53Z",
  "published" : "2024-04-05T15:08:53Z",
  "aliases" : [ ],
  "summary" : "eyre: Parts of Report are dropped as the wrong type during downcast",
  "details" : "In affected versions, after a `Report` is constructed using `wrap_err` or `wrap_err_with` to attach a message of type `D` onto an error of type `E`, then using `downcast` to recover ownership of either the value of type `D` or the value of type `E`, one of two things can go wrong:\n\n- If downcasting to `E`, there remains a value of type `D` to be dropped. It is incorrectly \"dropped\" by running `E`'s drop behavior, rather than `D`'s. For example if `D` is `&str` and `E` is `std::io::Error`, there would be a call of `std::io::Error::drop` in which the reference received by the `Drop` impl does not refer to a valid value of type `std::io::Error`, but instead to `&str`.\n\n- If downcasting to `D`, there remains a value of type `E` to be dropped. When `D` and `E` do not happen to be the same size, `E`'s drop behavior is incorrectly executed in the wrong location. The reference received by the `Drop` impl may point left or right of the real `E` value that is meant to be getting dropped.\n\nIn both cases, when the `Report` contains an error `E` that has nontrivial drop behavior, the most likely outcome is memory corruption.\n\nWhen the `Report` contains an error `E` that has trivial drop behavior (for example a `Utf8Error`) but where `D` has nontrivial drop behavior (such as `String`), the most likely outcome is that downcasting to `E` would leak `D`.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "crates.io",
      "name" : "eyre"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0.6.9"
      }, {
        "fixed" : "0.6.12"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/eyre-rs/eyre/issues/141"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/eyre-rs/eyre/commit/770ac3fa1435eae3b166a4b072053360e38a0575"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/eyre-rs/eyre"
  }, {
    "type" : "WEB",
    "url" : "https://rustsec.org/advisories/RUSTSEC-2024-0021.html"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-843" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2024-04-05T15:08:53Z",
    "nvd_published_at" : null
  }
}