# RUSTSEC-2022-0050: Interledger is Unmaintained

> The Interledger Rust library is unmaintained with unresolved security concerns, requiring users to migrate to alternative solutions.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Not stated
- **Victim action needed:** Not stated
- **Fix available:** No
- **Published:** 4 Aug 2022

## What is RUSTSEC-2022-0050?

RUSTSEC-2022-0050 is a vulnerability in interledger-packet, published on 4 Aug 2022. 

### Official description

Interledger family of crates is not being actively maintained anymore.

The owner of the published crate does not appear to be responsive.

There is an outstanding concern around username comparison.

This concern may or may not be resolved by bumping up the dependencies of the project.

## Which versions are affected by RUSTSEC-2022-0050?

1 open source package ship an affected version, including interledger-packet.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `interledger-packet` | crates.io | From 0.0.0-0 | None |

## How do I fix RUSTSEC-2022-0050?

No fix has been published for RUSTSEC-2022-0050 yet. Limit exposure of the affected software until one is available.

## Is RUSTSEC-2022-0050 being exploited?

There is no known exploitation of RUSTSEC-2022-0050 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for RUSTSEC-2022-0050 and fix it if it is affected.

What it is: RUSTSEC-2022-0050 is a vulnerability in interledger-packet, published on 4 Aug 2022. 
Exploitation: There is no known exploitation of RUSTSEC-2022-0050 in the wild and no public exploit code.

Affected packages and fixed versions:
- interledger-packet (crates.io): affected from 0.0.0-0; no fix listed

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/RUSTSEC-2022-0050/ (Markdown: https://insights.sbomify.com/RUSTSEC-2022-0050/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/RUSTSEC-2022-0050

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