Skip to content

Rust Failure Crate Vulnerable to Type confusion

Critical severity GitHub Reviewed Published Aug 25, 2021 to the GitHub Advisory Database • Updated Nov 9, 2023

Package

cargo failure (Rust)

Affected versions

<= 0.1.8

Patched versions

None

Description

Safe Rust code can implement malfunctioning __private_get_type_id__ and cause type confusion when downcasting, which is an undefined behavior.

Users who derive Fail trait are not affected.

References

Published by the National Vulnerability Database Dec 31, 2020
Reviewed Aug 19, 2021
Published to the GitHub Advisory Database Aug 25, 2021
Last updated Nov 9, 2023

Severity

Critical

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS score

0.235%
(63rd percentile)

Weaknesses

CVE ID

CVE-2019-25010

GHSA ID

GHSA-r98r-j25q-rmpr
Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.