# CVE-2019-0212: Improper Authorization in org.apache.hbase:hbase

> Attackers can bypass user-specific permissions in Apache HBase REST server, executing actions with server-level privileges when specific authentication configurations are enabled.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 Mar 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-535v-4x9q-446c

## What is CVE-2019-0212?

CVE-2019-0212 is a high-severity missing authorization vulnerability in Apache HBase, published on 28 Mar 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

In all previously released Apache HBase 2.x versions (2.0.0-2.0.4, 2.1.0-2.1.3), authorization was incorrectly applied to users of the HBase REST server. Requests sent to the HBase REST server were executed with the permissions of the REST server itself, not with the permissions of the end-user. This issue is only relevant when HBase is configured with Kerberos authentication, HBase authorization is enabled, and the REST server is configured with SPNEGO authentication. This issue does not extend beyond the HBase REST server.

## Which versions are affected by CVE-2019-0212?

4 open source packages ship an affected version, including org.apache.hbase:hbase. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.apache.hbase:hbase` | Maven | From 2.0.0 | 2.0.5 |
| `org.apache.hbase:hbase` | Maven | From 2.0.0 | 2.0.5 |
| `org.apache.hbase:hbase` | Maven | From 2.1.0 | 2.1.4 |
| `org.apache.hbase:hbase` | Maven | From 2.1.0 | 2.1.4 |

Products: Apache Hbase.

## How do I fix CVE-2019-0212?

Upgrade org.apache.hbase:hbase to a fixed version for your release line: 2.0.5 or 2.1.4.

## Is CVE-2019-0212 being exploited?

There is no known exploitation of CVE-2019-0212 in the wild and no public exploit code.

## Other vulnerabilities in Apache HBase

- [CVE-2018-8025](https://insights.sbomify.com/CVE-2018-8025/): Race condition in org.apache.hbase:hbase-thrift (high 8.1)
- [CVE-2019-15544](https://insights.sbomify.com/CVE-2019-15544/): Uncontrolled memory consumption in protobuf (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-2019-0212 and fix it if it is affected.

What it is: CVE-2019-0212 is a high-severity missing authorization vulnerability in Apache HBase, published on 28 Mar 2019. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-0212 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.apache.hbase:hbase (Maven): affected from 2.0.0; fixed in 2.0.5
- org.apache.hbase:hbase (Maven): affected from 2.0.0; fixed in 2.0.5
- org.apache.hbase:hbase (Maven): affected from 2.1.0; fixed in 2.1.4
- org.apache.hbase:hbase (Maven): affected from 2.1.0; fixed in 2.1.4

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-2019-0212/ (Markdown: https://insights.sbomify.com/CVE-2019-0212/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2019-0212
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-0212
- OSV: https://osv.dev/vulnerability/CVE-2019-0212

---
From sbomify Insights: https://insights.sbomify.com/CVE-2019-0212/
Summaries are generated and may contain mistakes; the official description above is the record.