# GHSA-h588-76vg-prgj: `DecimalArray` does not perform bound checks on accessing values and offsets

> Attackers can trigger out-of-bounds reads in safe code via malformed buffers, potentially leaking memory or causing crashes in applications using this Rust library.

- **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:** 14 Sep 2021
- **Also known as:** RUSTSEC-2021-0117

## What is GHSA-h588-76vg-prgj?

GHSA-h588-76vg-prgj is a memory corruption vulnerability in arrow, published on 14 Sep 2021. 

### Official description

`DecimalArray` performs insufficient bounds checks, which allows out-of-bounds reads in safe code if the lenght of the backing buffer is not a multiple of 16.

## Which versions are affected by GHSA-h588-76vg-prgj?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `arrow` | crates.io | All versions | 6.4.0 |
| `arrow` | crates.io | All versions | 6.4.0 |
| `arrow` | crates.io | From 0.0.0-0 | 6.4.0 |

## How do I fix GHSA-h588-76vg-prgj?

Upgrade arrow to 6.4.0 or later.

## Is GHSA-h588-76vg-prgj being exploited?

There is no known exploitation of GHSA-h588-76vg-prgj in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-h588-76vg-prgj and fix it if it is affected.

What it is: GHSA-h588-76vg-prgj is a memory corruption vulnerability in arrow, published on 14 Sep 2021. 
Exploitation: There is no known exploitation of GHSA-h588-76vg-prgj in the wild and no public exploit code.

Affected packages and fixed versions:
- arrow (crates.io): affected all versions; fixed in 6.4.0
- arrow (crates.io): affected all versions; fixed in 6.4.0
- arrow (crates.io): affected from 0.0.0-0; fixed in 6.4.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/GHSA-h588-76vg-prgj/ (Markdown: https://insights.sbomify.com/GHSA-h588-76vg-prgj/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-h588-76vg-prgj

---
From sbomify Insights: https://insights.sbomify.com/GHSA-h588-76vg-prgj/
Summaries are generated and may contain mistakes; the official description above is the record.