CVE-2018-8025

Race condition in org.apache.hbase:hbase-thrift

An issue in Apache HBase affects the optional "Thrift 1" API server when running over HTTP. There is a race-condition which could lead to authenticated sessions being incorrectly applied to users, e.g. one authenticated user would be considered a different user or an unauthenticated user would be treated as an authenticated user. https://issues.apache.org/jira/browse/HBASE-20664 implements a fix for this issue. It has been fixed in versions: 1.2.6.1, 1.3.2.1, 1.4.5, 2.0.1.

Multiple concurrent operations access a shared resource without proper synchronization, producing unpredictable results depending on timing. Typical impact: TOCTOU exploits, data corruption, or privilege escalation.

CVE-2018-8025 has a CVSS score of 8.1 (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 (2.0.1, 1.4.5, 1.3.2.1, 1.2.6.1); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

1. What is CVE-2018-8025? CVE-2018-8025 is a high-severity race condition vulnerability in org.apache.hbase:hbase-thrift (maven), affecting versions = 2.0.0. It is fixed in 2.0.1, 1.4.5, 1.3.2.1, 1.2.6.1. Multiple concurrent operations access a shared resource without proper synchronization, producing unpredictable results depending on timing.
2. How severe is CVE-2018-8025? CVE-2018-8025 has a CVSS score of 8.1 (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.
3. Which versions of org.apache.hbase:hbase-thrift are affected by CVE-2018-8025? org.apache.hbase:hbase-thrift (maven) versions = 2.0.0 is affected.
4. Is there a fix for CVE-2018-8025? Yes. CVE-2018-8025 is fixed in 2.0.1, 1.4.5, 1.3.2.1, 1.2.6.1. Upgrade to this version or later.
5. Is CVE-2018-8025 exploitable, and should I be worried? Whether CVE-2018-8025 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
6. What actually determines whether CVE-2018-8025 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.
7. How do I fix CVE-2018-8025?
   • Upgrade org.apache.hbase:hbase-thrift to 2.0.1 or later
   • Upgrade org.apache.hbase:hbase-thrift to 1.4.5 or later
   • Upgrade org.apache.hbase:hbase-thrift to 1.3.2.1 or later
   • Upgrade org.apache.hbase:hbase-thrift to 1.2.6.1 or later