# CVE-2018-8025: Race condition in org.apache.hbase:hbase-thrift > A race condition in the optional Thrift 1 API server allows attackers to hijack authenticated sessions or gain unauthorized access. - **Severity:** High 8.1 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/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:** 27 Jun 2018 - **Updated:** 16 Sep 2024 - **Also known as:** GHSA-r86j-2gc6-2cq9 ## What is CVE-2018-8025? CVE-2018-8025 is a high-severity vulnerability in Apache HBase, published on 27 Jun 2018. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description CVE-2018-8025 describes an issue in Apache HBase that 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. Weakness: CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization) ## Which versions are affected by CVE-2018-8025? 8 open source packages ship an affected version, including org.apache.hbase:hbase-thrift. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.apache.hbase:hbase-thrift` | Maven | All versions | 1.2.6.1 | | `org.apache.hbase:hbase-thrift` | Maven | All versions | 1.2.6.1 | | `org.apache.hbase:hbase-thrift` | Maven | From 1.3.0 | 1.3.2.1 | | `org.apache.hbase:hbase-thrift` | Maven | From 1.3.0 | 1.3.2.1 | | `org.apache.hbase:hbase-thrift` | Maven | From 1.4.0 | 1.4.5 | | `org.apache.hbase:hbase-thrift` | Maven | From 1.4.0 | 1.4.5 | | `org.apache.hbase:hbase-thrift` | Maven | From 2.0.0 | 2.0.1 | | `org.apache.hbase:hbase-thrift` | Maven | From 2.0.0 | 2.0.1 | Products: Apache Hbase. ## How do I fix CVE-2018-8025? Upgrade org.apache.hbase:hbase-thrift to a fixed version for your release line: 1.2.6.1, 1.3.2.1, 1.4.5 or 2.0.1. ## Is CVE-2018-8025 being exploited? There is no known exploitation of CVE-2018-8025 in the wild and no public exploit code. ## Other vulnerabilities in Apache HBase - [CVE-2019-15544](https://insights.sbomify.com/CVE-2019-15544/): Uncontrolled memory consumption in protobuf (high 7.5) - [CVE-2019-0212](https://insights.sbomify.com/CVE-2019-0212/): Improper Authorization in org.apache.hbase:hbase (high 7.5) - [CVE-2015-1836](https://insights.sbomify.com/CVE-2015-1836/): High severity vulnerability that affects org.apache.hbase:hbase (high 7.3) - [CVE-2026-49326](https://insights.sbomify.com/CVE-2026-49326/): Apache HBase: Missing scanner instance owner check in thrift delegation service (medium 6.5) - [CVE-2013-2193](https://insights.sbomify.com/CVE-2013-2193/): Security feature bypass in n/a (medium 4.3) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2018-8025 and fix it if it is affected. What it is: CVE-2018-8025 is a high-severity vulnerability in Apache HBase, published on 27 Jun 2018. 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-2018-8025 in the wild and no public exploit code. Affected packages and fixed versions: - org.apache.hbase:hbase-thrift (Maven): affected all versions; fixed in 1.2.6.1 - org.apache.hbase:hbase-thrift (Maven): affected all versions; fixed in 1.2.6.1 - org.apache.hbase:hbase-thrift (Maven): affected from 1.3.0; fixed in 1.3.2.1 - org.apache.hbase:hbase-thrift (Maven): affected from 1.3.0; fixed in 1.3.2.1 - org.apache.hbase:hbase-thrift (Maven): affected from 1.4.0; fixed in 1.4.5 - org.apache.hbase:hbase-thrift (Maven): affected from 1.4.0; fixed in 1.4.5 - org.apache.hbase:hbase-thrift (Maven): affected from 2.0.0; fixed in 2.0.1 - org.apache.hbase:hbase-thrift (Maven): affected from 2.0.0; fixed in 2.0.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-2018-8025/ (Markdown: https://insights.sbomify.com/CVE-2018-8025/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2018-8025 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-8025 - OSV: https://osv.dev/vulnerability/CVE-2018-8025 --- From sbomify Insights: https://insights.sbomify.com/CVE-2018-8025/ Summaries are generated and may contain mistakes; the official description above is the record.