What is CVE-2019-12410?

CVE-2019-12410 is a high-severity security vulnerability in red-arrow (rubygems), affecting versions >= 0.12.0, < 0.15.1. It is fixed in 0.15.1.

How severe is CVE-2019-12410?

CVE-2019-12410 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which packages are affected by CVE-2019-12410?

red-arrow (rubygems) versions >= 0.12.0, = 0.12.0, < 0.15.1.

Is there a fix for CVE-2019-12410?

Yes. CVE-2019-12410 is fixed in 0.15.1. Upgrade to this version or later.

Is CVE-2019-12410 exploitable, and should I be worried?

Whether CVE-2019-12410 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2019-12410 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2019-12410?

Upgrade: red-arrow to 0.15.1 or later, pyarrow to 0.15.1 or later.

CVE-2019-12410 in red-arrow | Intelligent Application Security

Q: How severe is CVE-2019-12410?

CVE-2019-12410 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which packages are affected by CVE-2019-12410?

red-arrow (rubygems) versions >= 0.12.0, = 0.12.0, < 0.15.1.

Q: Is there a fix for CVE-2019-12410?

Yes. CVE-2019-12410 is fixed in 0.15.1. Upgrade to this version or later.

Q: Is CVE-2019-12410 exploitable, and should I be worried?

Whether CVE-2019-12410 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2019-12410 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2019-12410?

Upgrade: red-arrow to 0.15.1 or later, pyarrow to 0.15.1 or later.

Summary

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.

Impact

CVE-2019-12410 has a CVSS score of 7.5 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.15.1); upgrading removes the vulnerable code path.

Affected versions

red-arrow (>= 0.12.0, < 0.15.1) pyarrow (>= 0.12.0, < 0.15.1)

Security releases

red-arrow → 0.15.1 (rubygems) pyarrow → 0.15.1 (pip)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

See it in your environment

Remediation advice

Upgrade the following packages to resolve this vulnerability:

red-arrow to 0.15.1 or later; pyarrow to 0.15.1 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2019-12410? CVE-2019-12410 is a high-severity security vulnerability in red-arrow (rubygems), affecting versions >= 0.12.0, < 0.15.1. It is fixed in 0.15.1.
How severe is CVE-2019-12410? CVE-2019-12410 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which packages are affected by CVE-2019-12410?
- red-arrow (rubygems) (versions >= 0.12.0, < 0.15.1)
- pyarrow (pip) (versions >= 0.12.0, < 0.15.1)
Is there a fix for CVE-2019-12410? Yes. CVE-2019-12410 is fixed in 0.15.1. Upgrade to this version or later.
Is CVE-2019-12410 exploitable, and should I be worried? Whether CVE-2019-12410 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2019-12410 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2019-12410?
- Upgrade red-arrow to 0.15.1 or later
- Upgrade pyarrow to 0.15.1 or later

Other vulnerabilities in red-arrow

CVE-2019-12408