Skip to content

Improper privilege handling in Apache Accumulo

High severity GitHub Reviewed Published Feb 9, 2022 to the GitHub Advisory Database • Updated Jan 31, 2024

Package

maven org.apache.accumulo:accumulo-master (Maven)

Affected versions

>= 1.5.0, < 1.10.1
= 2.0.0

Patched versions

1.10.1
2.0.1

Description

Apache Accumulo versions 1.5.0 through 1.10.0 and version 2.0.0 do not properly check the return value of some policy enforcement functions before permitting an authenticated user to perform certain administrative operations. Specifically, the return values of the 'canFlush' and 'canPerformSystemActions' security functions are not checked in some instances, therefore allowing an authenticated user with insufficient permissions to perform the following actions: flushing a table, shutting down Accumulo or an individual tablet server, and setting or removing system-wide Accumulo configuration properties.

References

Published by the National Vulnerability Database Dec 29, 2020
Reviewed Apr 7, 2021
Published to the GitHub Advisory Database Feb 9, 2022
Last updated Jan 31, 2024

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H

EPSS score

0.125%
(48th percentile)

Weaknesses

CVE ID

CVE-2020-17533

GHSA ID

GHSA-grc3-8q8m-4j7c

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.