HbaseApplication · Apache
CVE-2018-8025
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 · uneditedCVE-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.
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 confidenceApache HBase contains a race condition in the optional Thrift 1 API server when running over HTTP transport. This flaw can cause authentication session state to be incorrectly shared between users, potentially allowing one authenticated user to inherit another user's identity or an unauthenticated user to be incorrectly treated as authenticated.
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
HbaseApplication
> 1.0.0, <= 2.0.0= 0.92.0CVSS 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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed HBase versionRun 'hbase version' or check the HBase jars and pom.xml files in your installation directoryAffected if Version is greater than 1.0.0 and less than or equal to 2.0.0, or version equals 0.92.0
-
Confirm Thrift 1 server is enabledCheck HBase configuration files (hbase-site.xml) for 'hbase.thrift.info.port' and 'hbase.thrift.info.bindAddress' settings, or look for ThriftServer startup scripts/processesAffected if Thrift 1 server (ThriftServer) is configured and running as a daemon service
-
Verify HTTP transport is in useExamine the Thrift server启动参数 or configuration for 'hbase.thrift.info.port' - HTTP mode typically uses port 9095 by default, or check for 'hbase.thrift.http' set to true in hbase-site.xmlAffected if Thrift 1 server is configured to use HTTP transport rather than TCP transport
-
Check for active Thrift HTTP sessionsReview Thrift HTTP access logs if available, or monitor network connections on the Thrift HTTP port to observe active sessionsAffected if Multiple users are authenticating and maintaining concurrent sessions through the Thrift 1 HTTP interface
Environment is affected if running a vulnerable HBase version (0.92.0 or >1.0.0 through 2.0.0) with the Thrift 1 server enabled and configured to use HTTP transport.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade to Apache HBase versions 1.2.6.1, 1.3.2.1, 1.4.5, or 2.0.1 which contain the fix. If immediate upgrade is not feasible, disable the Thrift 1 HTTP server and use Thrift over TCP transport or Thrift 2 as alternative.
Fix this in Hbase
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-8025 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2018-8025 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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