# RUSTSEC-2023-0126: Aliasing violation in `OrdSet` insertion

> Undefined behavior in im::OrdSet insertion allows memory corruption, potentially leading to code execution or crashes in applications using this unmaintained Rust library.

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

## What is RUSTSEC-2023-0126?

RUSTSEC-2023-0126 is a memory corruption vulnerability in im, published on 4 Feb 2023. 

### Official description

Inserting into an `im::OrdSet` (for example by collecting an iterator into one) can violate
Rust's aliasing rules: Miri reports a stacked borrows violation in
`sized_chunks::Chunk::force_copy()`, which is called during insertion, where a shared borrow
is invalidated by a unique borrow before the read through it completes.
This is undefined behavior, reachable from safe code.

No fixed version is available, as the crate is unmaintained; its GitHub
repository was archived by the owner on 2026-05-03.

## Which versions are affected by RUSTSEC-2023-0126?

1 open source package ship an affected version, including im.


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

## How do I fix RUSTSEC-2023-0126?

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

## Is RUSTSEC-2023-0126 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for RUSTSEC-2023-0126 and fix it if it is affected.

What it is: RUSTSEC-2023-0126 is a memory corruption vulnerability in im, published on 4 Feb 2023. 
Exploitation: There is no known exploitation of RUSTSEC-2023-0126 in the wild and no public exploit code.

Affected packages and fixed versions:
- im (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-2023-0126/ (Markdown: https://insights.sbomify.com/RUSTSEC-2023-0126/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/RUSTSEC-2023-0126

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