CVE Vulnerabilities

CVE-2019-0201

Missing Authorization

Published: May 23, 2019 | Modified: Nov 07, 2023
CVSS 3.x
5.9
MEDIUM
Source:
NVD
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
CVSS 2.x
4.3 MEDIUM
AV:N/AC:M/Au:N/C:P/I:N/A:N
RedHat/V2
RedHat/V3
7.5 IMPORTANT
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Ubuntu
LOW

An issue is present in Apache ZooKeeper 1.0.0 to 3.4.13 and 3.5.0-alpha to 3.5.4-beta. ZooKeeper’s getACL() command doesn’t check any permission when retrieves the ACLs of the requested node and returns all information contained in the ACL Id field as plaintext string. DigestAuthenticationProvider overloads the Id field with the hash value that is used for user authentication. As a consequence, if Digest Authentication is in use, the unsalted hash value will be disclosed by getACL() request for unauthenticated or unprivileged users.

Weakness

The product does not perform an authorization check when an actor attempts to access a resource or perform an action.

Affected Software

Name Vendor Start Version End Version
Activemq Apache 5.15.9 (including) 5.15.9 (including)
Drill Apache 1.16.0 (including) 1.16.0 (including)
Zookeeper Apache 1.0.0 (including) 3.4.13 (including)
Zookeeper Apache 3.5.0 (including) 3.5.0 (including)
Zookeeper Apache 3.5.0-alpha (including) 3.5.0-alpha (including)
Zookeeper Apache 3.5.0-rc0 (including) 3.5.0-rc0 (including)
Zookeeper Apache 3.5.1 (including) 3.5.1 (including)
Zookeeper Apache 3.5.1-alpha (including) 3.5.1-alpha (including)
Zookeeper Apache 3.5.1-rc0 (including) 3.5.1-rc0 (including)
Zookeeper Apache 3.5.1-rc1 (including) 3.5.1-rc1 (including)
Zookeeper Apache 3.5.1-rc2 (including) 3.5.1-rc2 (including)
Zookeeper Apache 3.5.1-rc3 (including) 3.5.1-rc3 (including)
Zookeeper Apache 3.5.1-rc4 (including) 3.5.1-rc4 (including)
Zookeeper Apache 3.5.2 (including) 3.5.2 (including)
Zookeeper Apache 3.5.2-alpha (including) 3.5.2-alpha (including)
Zookeeper Apache 3.5.2-rc0 (including) 3.5.2-rc0 (including)
Zookeeper Apache 3.5.2-rc1 (including) 3.5.2-rc1 (including)
Zookeeper Apache 3.5.3 (including) 3.5.3 (including)
Zookeeper Apache 3.5.3-beta (including) 3.5.3-beta (including)
Zookeeper Apache 3.5.3-rc0 (including) 3.5.3-rc0 (including)
Zookeeper Apache 3.5.3-rc1 (including) 3.5.3-rc1 (including)
Zookeeper Apache 3.5.4-beta (including) 3.5.4-beta (including)
Red Hat Fuse 6.3 RedHat zookeeper *
Red Hat Fuse 6.3 RedHat zookeeper *
Red Hat Fuse 7.5.0 RedHat zookeeper *
Red Hat JBoss Data Virtualization 6.4.8 RedHat zookeeper *
Zookeeper Ubuntu bionic *
Zookeeper Ubuntu cosmic *
Zookeeper Ubuntu disco *
Zookeeper Ubuntu eoan *
Zookeeper Ubuntu esm-apps/xenial *
Zookeeper Ubuntu trusty *
Zookeeper Ubuntu trusty/esm *
Zookeeper Ubuntu upstream *
Zookeeper Ubuntu xenial *

Extended Description

Assuming a user with a given identity, authorization is the process of determining whether that user can access a given resource, based on the user’s privileges and any permissions or other access-control specifications that apply to the resource. When access control checks are not applied, users are able to access data or perform actions that they should not be allowed to perform. This can lead to a wide range of problems, including information exposures, denial of service, and arbitrary code execution.

Potential Mitigations

  • Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) [REF-229] to enforce the roles at the appropriate boundaries.
  • Note that this approach may not protect against horizontal authorization, i.e., it will not protect a user from attacking others with the same role.
  • Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
  • For example, consider using authorization frameworks such as the JAAS Authorization Framework [REF-233] and the OWASP ESAPI Access Control feature [REF-45].
  • For web applications, make sure that the access control mechanism is enforced correctly at the server side on every page. Users should not be able to access any unauthorized functionality or information by simply requesting direct access to that page.
  • One way to do this is to ensure that all pages containing sensitive information are not cached, and that all such pages restrict access to requests that are accompanied by an active and authenticated session token associated with a user who has the required permissions to access that page.

References