ArrowApplication · Apache

CVE-2019-12408

HIGH · 7.5 CVSS v3.1 Published 2019-11-08
Fix available
A fix is available. Upgrade to after 0.14.1 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
It was discovered that the C++ implementation (which underlies the R, Python and Ruby implementations) of Apache Arrow 0.14.0 to 0.14.1 had a uninitialized memory bug when building arrays with null values in some cases. This can lead to uninitialized memory being unintentionally shared if Arrow Arrays are transmitted over the wire (for instance with Flight) or persisted in the streaming IPC and file formats.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

An uninitialized memory bug exists in Apache Arrow 0.14.0-0.14.1's C++ implementation (affecting R, Python, Ruby bindings) where building arrays with null values can cause uninitialized memory contents to be included in array data. When these arrays are transmitted over network protocols (like Flight) or persisted to disk (IPC/file formats), this can lead to unintentional disclosure of sensitive memory contents.

MitigationUpgrade to Apache Arrow 0.14.2 or later which contains the fix. Identify all systems using affected versions and test to ensure the upgrade does not break functionality.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
ArrowApplication
Affected:>= 0.14.0, <= 0.14.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Apache Arrow C++ library version
    Query the installed Arrow C++ library version using your package manager or by checking the library metadata (e.g., pkg-config --modversion arrow, or inspect the shared library file version)
    Affected if The version is >= 0.14.0 and <= 0.14.1
  2. Identify Python pyarrow binding version
    Run 'pip show pyarrow' or 'python -c import pyarrow; print(pyarrow.__version__)' to retrieve the pyarrow version
    Affected if pyarrow version corresponds to Arrow C++ 0.14.0-0.14.1 (typically shows 0.14.0 or 0.14.1)
  3. Identify R arrow package version
    Run 'packageVersion("arrow")' in R or check the installed package metadata
    Affected if R arrow package version corresponds to Arrow 0.14.0-0.14.1
  4. Identify Ruby arrow gem version
    Run 'gem list arrow' or check the Gemfile.lock for the arrow gem version
    Affected if Ruby arrow gem version corresponds to Arrow 0.14.0-0.14.1
  5. Verify if data is transmitted or persisted
    Inspect application code and configuration to determine if Arrow arrays containing null values are written to IPC files, Arrow files, or transmitted over Flight RPC
    Affected if The vulnerability is exploitable only when arrays with null values are written to disk (IPC/file formats) or sent over network protocols like Flight

You are affected if your environment has Apache Arrow 0.14.0-0.14.1 installed (C++ or any bindings) AND you transmit arrays over network protocols or persist them to disk.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to a release after 0.14.1
Interim mitigation

Upgrade to Apache Arrow 0.14.2 or later which contains the fix. Identify all systems using affected versions and test to ensure the upgrade does not break functionality.

Fix this in Arrow Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-12408 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-12408 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data