# OSV-2022-852: Security exception in java.base/java.nio.Bits.reserveMemory

> A security exception in Java NIO memory reservation can cause application crashes, impacting availability for Java applications using direct buffers.

- **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:** 7 Sep 2022

## What is OSV-2022-852?

OSV-2022-852 is a denial of service vulnerability in arrow-java, published on 7 Sep 2022. 

### Official description

OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=51044

```
Crash type: Security exception
Crash state:
java.base/java.nio.Bits.reserveMemory
java.base/java.nio.DirectByteBuffer.<init>
java.base/java.nio.ByteBuffer.allocateDirect
```

## Which versions are affected by OSV-2022-852?

1 open source package ship an affected version, including arrow-java.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `arrow-java` | OSS-Fuzz | All versions | None |

## How do I fix OSV-2022-852?

No fix has been published for OSV-2022-852 yet. Limit exposure of the affected software until one is available.

## Is OSV-2022-852 being exploited?

There is no known exploitation of OSV-2022-852 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for OSV-2022-852 and fix it if it is affected.

What it is: OSV-2022-852 is a denial of service vulnerability in arrow-java, published on 7 Sep 2022. 
Exploitation: There is no known exploitation of OSV-2022-852 in the wild and no public exploit code.

Affected packages and fixed versions:
- arrow-java (OSS-Fuzz): affected all versions; 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/OSV-2022-852/ (Markdown: https://insights.sbomify.com/OSV-2022-852/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/OSV-2022-852

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