# GHSA-jcr6-4frq-9gjj: Users vulnerable to unaligned read of `*const *const c_char` pointer

> An unaligned pointer dereference in the users crate causes undefined behavior, potentially leading to application crashes or panics.

- **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:** 10 Sep 2023
- **Also known as:** RUSTSEC-2023-0059

## What is GHSA-jcr6-4frq-9gjj?

GHSA-jcr6-4frq-9gjj is a memory corruption vulnerability in users, published on 10 Sep 2023. 

### Official description

Affected versions dereference a potentially unaligned pointer. The pointer is commonly unaligned in practice, resulting in undefined behavior.

In some build modes, this is observable as a panic followed by abort. In other build modes the UB may manifest in some other way, including the possibility of working correctly in some architectures.

The crate is not currently maintained, so a patched version is not available.

## Recommended alternatives
- [`uzers`](https://crates.io/crates/uzers) (an actively maintained fork of the `users` crate)
- [`sysinfo`](https://crates.io/crates/sysinfo)

## Which versions are affected by GHSA-jcr6-4frq-9gjj?

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


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

## How do I fix GHSA-jcr6-4frq-9gjj?

No fix has been published for GHSA-jcr6-4frq-9gjj yet. Limit exposure of the affected software until one is available.

## Is GHSA-jcr6-4frq-9gjj being exploited?

There is no known exploitation of GHSA-jcr6-4frq-9gjj in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-jcr6-4frq-9gjj and fix it if it is affected.

What it is: GHSA-jcr6-4frq-9gjj is a memory corruption vulnerability in users, published on 10 Sep 2023. 
Exploitation: There is no known exploitation of GHSA-jcr6-4frq-9gjj in the wild and no public exploit code.

Affected packages and fixed versions:
- users (crates.io): affected all versions up to 0.11.0; no fix listed
- users (crates.io): affected all versions up to 0.11.0; no fix listed
- users (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-jcr6-4frq-9gjj/ (Markdown: https://insights.sbomify.com/GHSA-jcr6-4frq-9gjj/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-jcr6-4frq-9gjj

---
From sbomify Insights: https://insights.sbomify.com/GHSA-jcr6-4frq-9gjj/
Summaries are generated and may contain mistakes; the official description above is the record.