# GHSA-wm8x-php5-hvq6: Maligned causes incorrect deallocation

> Incorrect memory deallocation in the maligned crate can lead to undefined behavior, potentially allowing 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:** 4 Mar 2023
- **Also known as:** RUSTSEC-2023-0017

## What is GHSA-wm8x-php5-hvq6?

GHSA-wm8x-php5-hvq6 is a memory corruption vulnerability in maligned, published on 4 Mar 2023. 

### Official description

`maligned::align_first` manually allocates with an alignment larger than T, and then uses `Vec::from_raw_parts` on that allocation to get a `Vec<T>`.

[`GlobalAlloc::dealloc`](https://doc.rust-lang.org/std/alloc/trait.GlobalAlloc.html#tymethod.dealloc) requires that the `layout` argument must be the same layout that was used to allocate that block of memory.

When deallocating, `Box` and `Vec` may not respect the specified alignment and can cause undefined behavior.

## Which versions are affected by GHSA-wm8x-php5-hvq6?

3 open source packages ship an affected version, including maligned.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `maligned` | crates.io | All versions to 0.2.1 | None |
| `maligned` | crates.io | All versions to 0.2.1 | None |
| `maligned` | crates.io | From 0.0.0-0 | None |

## How do I fix GHSA-wm8x-php5-hvq6?

No fix has been published for GHSA-wm8x-php5-hvq6 yet. Limit exposure of the affected software until one is available.

## Is GHSA-wm8x-php5-hvq6 being exploited?

There is no known exploitation of GHSA-wm8x-php5-hvq6 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-wm8x-php5-hvq6 and fix it if it is affected.

What it is: GHSA-wm8x-php5-hvq6 is a memory corruption vulnerability in maligned, published on 4 Mar 2023. 
Exploitation: There is no known exploitation of GHSA-wm8x-php5-hvq6 in the wild and no public exploit code.

Affected packages and fixed versions:
- maligned (crates.io): affected all versions up to 0.2.1; no fix listed
- maligned (crates.io): affected all versions up to 0.2.1; no fix listed
- maligned (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-wm8x-php5-hvq6/ (Markdown: https://insights.sbomify.com/GHSA-wm8x-php5-hvq6/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-wm8x-php5-hvq6

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