# CVE-2020-25575: Other in n/a

> The deprecated Rust failure crate contains a type confusion flaw during downcasting, potentially causing compatibility hazards in applications using it.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Sep 2020
- **Updated:** 4 Aug 2024
- **Also known as:** DEBIAN-CVE-2020-25575, UBUNTU-CVE-2020-25575

## What is CVE-2020-25575?

CVE-2020-25575 is a critical vulnerability in n/a, published on 14 Sep 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in the failure crate through 0.1.5 for Rust. It may introduce "compatibility hazards" in some applications, and has a type confusion flaw when downcasting. NOTE: This vulnerability only affects products that are no longer supported by the maintainer. NOTE: This may overlap CVE-2019-25010

Weakness: CWE-843 (Access of Resource Using Incompatible Type)

## Which versions are affected by CVE-2020-25575?

It affects 1 product.


Products: Failure Project Failure.

## How do I fix CVE-2020-25575?

No fix has been published for CVE-2020-25575 yet. Limit exposure of the affected software until one is available.

## Is CVE-2020-25575 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-25575 exists.

## Other vulnerabilities in n/a

- [CVE-2019-25010](https://insights.sbomify.com/CVE-2019-25010/): Other in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-25575 and fix it if it is affected.

What it is: CVE-2020-25575 is a critical vulnerability in n/a, published on 14 Sep 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-25575 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-25575/ (Markdown: https://insights.sbomify.com/CVE-2020-25575/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-25575
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-25575
- OSV: https://osv.dev/vulnerability/CVE-2020-25575

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-25575/
Summaries are generated and may contain mistakes; the official description above is the record.