# GHSA-f9g6-fp84-fv92: impl `FromMdbValue` for bool is unsound

> Unsound bool conversion in lmdb-rs allows memory corruption and undefined behavior, potentially leading to code execution 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:** No
- **Published:** 26 Jun 2023
- **Also known as:** RUSTSEC-2023-0047

## What is GHSA-f9g6-fp84-fv92?

GHSA-f9g6-fp84-fv92 is a memory corruption vulnerability in lmdb-rs, published on 26 Jun 2023. 

### Official description

The implementation of `FromMdbValue` has several unsoundness issues. First of all, it allows to reinterpret arbitrary bytes as a bool and could make undefined behavior happen with safe function. Secondly, it allows transmuting pointer without taking memory layout into consideration. The details of reproducing the bug are available [here](https://github.com/vhbit/lmdb-rs/issues/67).

## Which versions are affected by GHSA-f9g6-fp84-fv92?

3 open source packages ship an affected version, including lmdb-rs.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `lmdb-rs` | crates.io | All versions to 0.7.6 | None |
| `lmdb-rs` | crates.io | All versions to 0.7.6 | None |
| `lmdb-rs` | crates.io | From 0.0.0-0 | None |

## How do I fix GHSA-f9g6-fp84-fv92?

No fix has been published for GHSA-f9g6-fp84-fv92 yet. Limit exposure of the affected software until one is available.

## Is GHSA-f9g6-fp84-fv92 being exploited?

There is no known exploitation of GHSA-f9g6-fp84-fv92 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-f9g6-fp84-fv92 and fix it if it is affected.

What it is: GHSA-f9g6-fp84-fv92 is a memory corruption vulnerability in lmdb-rs, published on 26 Jun 2023. 
Exploitation: There is no known exploitation of GHSA-f9g6-fp84-fv92 in the wild and no public exploit code.

Affected packages and fixed versions:
- lmdb-rs (crates.io): affected all versions up to 0.7.6; no fix listed
- lmdb-rs (crates.io): affected all versions up to 0.7.6; no fix listed
- lmdb-rs (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/GHSA-f9g6-fp84-fv92/ (Markdown: https://insights.sbomify.com/GHSA-f9g6-fp84-fv92/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-f9g6-fp84-fv92

---
From sbomify Insights: https://insights.sbomify.com/GHSA-f9g6-fp84-fv92/
Summaries are generated and may contain mistakes; the official description above is the record.