# RUSTSEC-2025-0171: soundness issue

> A soundness issue in the mod3d_base Rust library allows unsafe pointer calculations via unchecked byte offsets, potentially leading to memory corruption or crashes.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Not stated
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 6 May 2025

## What is RUSTSEC-2025-0171?

RUSTSEC-2025-0171 is a memory corruption vulnerability in mod3d-base, published on 6 May 2025. 

### Official description

`mod3d_base::BufferData::as_ptr` lack of sufficient checks to its public self field `byte_offset` and used unsafely to do the pointer calculation.

## Which versions are affected by RUSTSEC-2025-0171?

1 open source package ship an affected version, including mod3d-base.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `mod3d-base` | crates.io | From 0.0.0-0 | 0.3.0 |

## How do I fix RUSTSEC-2025-0171?

Upgrade mod3d-base to 0.3.0 or later.

## Is RUSTSEC-2025-0171 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for RUSTSEC-2025-0171 and fix it if it is affected.

What it is: RUSTSEC-2025-0171 is a memory corruption vulnerability in mod3d-base, published on 6 May 2025. 
Exploitation: There is no known exploitation of RUSTSEC-2025-0171 in the wild and no public exploit code.

Affected packages and fixed versions:
- mod3d-base (crates.io): affected from 0.0.0-0; fixed in 0.3.0

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

## Sources

- OSV: https://osv.dev/vulnerability/RUSTSEC-2025-0171

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