Alluxio uses com.google.guava:guava:14.0.1 which has security vulnerability

Description

Alluxio uses com.google.guava:guava:14.0.1 which has following security vulnerability.
Vulnerability details:
Number:CVE‌-2018-10237
Description:
Unbounded memory allocation in Google Guava 11.0 through 24.x before 24.1.1 allows remote attackers to conduct denial of service attacks against servers that depend on this library and deserialize attacker-provided data, because the AtomicDoubleArray class (when serialized with Java serialization) and the CompoundOrdering class (when serialized with GWT serialization) perform eager allocation without appropriate checks on what a client has sent and whether the data size is reasonable
(source:https://www.cvedetails.com/cve/CVE-2018-10237/?q=CVE‌-2018-10237)

Is there any upgrade/alternate planned for above issue?

Environment

None

Activity

Show:
Bin Fan
October 1, 2018, 6:24 PM

we should address this issue in 2.0, ?

Andrew Audibert
October 1, 2018, 6:33 PM

I would be on board with upgrading to the latest Guava. It isn’t part of our public API, so we could shade/relocate it in the client to avoid conflicting with the Guava used by hdfs/spark/etc.

Andrew Audibert
October 1, 2018, 6:34 PM

Anyway, I don’t think this security issue affects us because we don’t use Guava to deserialize external data.

Bin Fan
October 1, 2018, 6:41 PM

+1 for shading Guava in client jar after upgrading to latest Guava.

Even the codebase currently is not affected by the security vulnerability hypothetically, it is risky to continue with the vulnerability unaddressed. In addition, Guava 14.0 is considered very old now.

I will create a Jira on this.

Configure