Skip to content
Fencer Intel
high 7.3

CVE-2015-1836 json

High severity vulnerability that affects org.apache.hbase:hbase

published 2015-12-21 10 y ago modified 2026-06-17 4 mo ago also GHSA-p8xr-4v2c-rvgp , EUVD-2018-0650

cvss
7.3
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
7.4%
EPSS 7.4% chance of exploitation in 30 days, percentile 94%
public exploits
0
none known

Summary

Apache HBase 0.98 before 0.98.12.1, 1.0 before 1.0.1.1, and 1.1 before 1.1.0.1, as used in IBM InfoSphere BigInsights 3.0, 3.0.0.1, and 3.0.0.2 and other products, uses incorrect ACLs for ZooKeeper coordination state, which allows remote attackers to cause a denial of service (daemon outage), obtain sensitive information, or modify data via unspecified client traffic.

Patch / fix

  • maven org.apache.hbase:hbase 0.98.12.1, 1.0.1.1, 1.1.0.1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2015-1836 updated cvss 6.8

HBase: insecure ACLs in ZooKeeper

  • Red Hat JBoss Fuse 6 camel-hbase camel-hbase Red Hat JBoss Fuse Service Works 6 camel-hbase camel-hbase Red Hat OpenShift Enterprise 2 camel-hbase camel-hbase
    affected: no fix available

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

7.42% chance of exploitation in the next 30 days, higher than 94% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.0 7.3 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
NVD 2.0 7.5 AV:N/AC:L/Au:N/C:P/I:P/A:P
GitHub 3.0 7.3 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

Affected packages

ecosystem package affected fixed in
maven org.apache.hbase:hbase
>=0.98, <0.98.12.1
>=1.0.0, <1.0.1.1
>=1.1.0, <1.1.0.1
0.98.12.1
1.0.1.1
1.1.0.1

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.