# CVE-2019-12410: Missing Initialization of Resource in Apache Arrow

> Apache Arrow fails to initialize memory when reading RLE null data from Parquet, potentially exposing uninitialized memory to attackers via data transmission or storage.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 8 Nov 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-cjw4-2w9r-r8mv, PYSEC-2019-196

## What is CVE-2019-12410?

CVE-2019-12410 is a high-severity vulnerability in Apache Arrow, published on 8 Nov 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

While investigating UBSAN errors in https://github.com/apache/arrow/pull/5365 it was discovered Apache Arrow versions 0.12.0 to 0.14.1, left memory Array data uninitialized when reading RLE null data from parquet. This affected the C++, Python, Ruby and R implementations. The uninitialized memory could potentially be shared if are transmitted over the wire (for instance with Flight) or persisted in the streaming IPC and file formats.

Weakness: CWE-909 (Missing Initialization of Resource)

## Which versions are affected by CVE-2019-12410?

5 open source packages ship an affected version, including pyarrow and red-arrow. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `pyarrow` | PyPI | From 0.12.0 | 0.15.0 |
| `pyarrow` | PyPI | From 0.12.0 | 0.15.1 |
| `pyarrow` | PyPI | From 0.12.0 | 0.15.1 |
| `red-arrow` | RubyGems | From 0.12.0 | 0.15.1 |
| `red-arrow` | RubyGems | From 0.12.0 | 0.15.1 |

Products: Apache Arrow.

## How do I fix CVE-2019-12410?

Upgrade pyarrow to a fixed version for your release line: 0.15.0 or 0.15.1.

## Is CVE-2019-12410 being exploited?

There is no known exploitation of CVE-2019-12410 in the wild and no public exploit code.

## Other vulnerabilities in Apache Arrow

- [CVE-2024-52338](https://insights.sbomify.com/CVE-2024-52338/): Apache Arrow R package: Arbitrary code execution when loading a malicious data file (critical 9.8)
- [CVE-2024-41178](https://insights.sbomify.com/CVE-2024-41178/): Apache Arrow Rust Object Store: AWS WebIdentityToken exposure in log files (high 7.5)
- [CVE-2019-12408](https://insights.sbomify.com/CVE-2019-12408/): Missing Initialization of Resource in Apache Arrow (high 7.5)
- [CVE-2026-25087](https://insights.sbomify.com/CVE-2026-25087/): Apache Arrow: Potential use-after-free when reading IPC file with pre-buffering (high 7.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-12410 and fix it if it is affected.

What it is: CVE-2019-12410 is a high-severity vulnerability in Apache Arrow, published on 8 Nov 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-12410 in the wild and no public exploit code.

Affected packages and fixed versions:
- pyarrow (PyPI): affected from 0.12.0; fixed in 0.15.0
- pyarrow (PyPI): affected from 0.12.0; fixed in 0.15.1
- pyarrow (PyPI): affected from 0.12.0; fixed in 0.15.1
- red-arrow (RubyGems): affected from 0.12.0; fixed in 0.15.1
- red-arrow (RubyGems): affected from 0.12.0; fixed in 0.15.1

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/CVE-2019-12410/ (Markdown: https://insights.sbomify.com/CVE-2019-12410/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2019-12410
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-12410
- OSV: https://osv.dev/vulnerability/CVE-2019-12410

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