# RUSTSEC-2024-0425: get-size is unmaintained

> The get-size Rust library is unmaintained and depends on yanked crates, posing supply chain risks; developers should migrate to alternatives.

- **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:** 15 Sep 2024

## What is RUSTSEC-2024-0425?

RUSTSEC-2024-0425 is a vulnerability in get-size, published on 15 Sep 2024. 

### Official description

get-size's maintainer seems to be unreachable, with no commits and releases pushed for 1 year and no activity on the GitHub repo.

get-size also depends on `get-size-derive 0.1.3`, which uses `attribute-derive ^0.6` a version of the crate which uses the yanked crate `proc-macro-error`.

## Possible Alternative(s)

- [get-size2](https://crates.io/crates/get-size2)
- [typesize](https://crates.io/crates/typesize)

## Which versions are affected by RUSTSEC-2024-0425?

1 open source package ship an affected version, including get-size.


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

## How do I fix RUSTSEC-2024-0425?

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

## Is RUSTSEC-2024-0425 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for RUSTSEC-2024-0425 and fix it if it is affected.

What it is: RUSTSEC-2024-0425 is a vulnerability in get-size, published on 15 Sep 2024. 
Exploitation: There is no known exploitation of RUSTSEC-2024-0425 in the wild and no public exploit code.

Affected packages and fixed versions:
- get-size (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-2024-0425/ (Markdown: https://insights.sbomify.com/RUSTSEC-2024-0425/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/RUSTSEC-2024-0425

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