CVE-2019-0201 Details

CVE-2019-0201

Published: 2019-05-23
Last Modified: 2021-08-16
CVE Author: NIST National Vulnerability Database
CVE Assigner: security@apache.org
Summary

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.

Analysis
Common Vulnerability Score System v2.0
Severity Medium
Base Score 4.3/10
Exploit Score 8.6/10
Access Vector Network
Access Complexity Medium
Authentication None
Impact Score 2.9/10
Confidentiality Impact Partial
Availability Impact None
Integrity Impact None
Vector String AV:N/AC:M/Au:N/C:P/I:N/A:N
Common Vulnerability Score System v3.1
Severity Medium
Base Score 5.9/10
Exploit Score 2.2/10
Access Vector Network
Access Complexity High
Privileges Required None
Impact Score 3.6/10
Confidentiality Impact High
Availability Impact None
Integrity Impact None
Scope Unchanged
User Interaction None
Vector String CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
Products Reported
CPE Vulnerable Start Excluding
cpe:2.3:a:apache:zookeeper:3.5.0:alpha:*:*:*:*:*:* Yes - -
cpe:2.3:a:apache:zookeeper:3.5.0:rc0:*:*:*:*:*:* Yes - -
cpe:2.3:a:apache:zookeeper:3.5.1:rc3:*:*:*:*:*:* Yes - -
cpe:2.3:a:apache:zookeeper:3.5.1:rc4:*:*:*:*:*:* Yes - -
cpe:2.3:a:apache:zookeeper:3.5.3:rc1:*:*:*:*:*:* Yes - -
cpe:2.3:a:apache:zookeeper:3.5.4:beta:*:*:*:*:*:* Yes - -
cpe:2.3:a:apache:zookeeper:3.5.1:alpha:*:*:*:*:*:* Yes - -
cpe:2.3:a:apache:zookeeper:3.5.1:rc0:*:*:*:*:*:* Yes - -
cpe:2.3:a:apache:zookeeper:3.5.2:rc1:*:*:*:*:*:* Yes - -
cpe:2.3:a:apache:zookeeper:3.5.3:-:*:*:*:*:*:* Yes - -
cpe:2.3:a:apache:zookeeper:*:*:*:*:*:*:*:* Yes 1.0.0 -
cpe:2.3:a:apache:zookeeper:3.5.1:rc1:*:*:*:*:*:* Yes - -
cpe:2.3:a:apache:zookeeper:3.5.1:rc2:*:*:*:*:*:* Yes - -
cpe:2.3:a:apache:zookeeper:3.5.3:beta:*:*:*:*:*:* Yes - -
cpe:2.3:a:apache:zookeeper:3.5.3:rc0:*:*:*:*:*:* Yes - -
cpe:2.3:a:apache:zookeeper:3.5.0:-:*:*:*:*:*:* Yes - -
cpe:2.3:a:apache:zookeeper:3.5.1:-:*:*:*:*:*:* Yes - -
cpe:2.3:a:apache:zookeeper:3.5.2:-:*:*:*:*:*:* Yes - -
cpe:2.3:a:apache:zookeeper:3.5.2:alpha:*:*:*:*:*:* Yes - -
cpe:2.3:a:apache:zookeeper:3.5.2:rc0:*:*:*:*:*:* Yes - -
cpe:2.3:o:debian:debian_linux:8.0:*:*:*:*:*:*:* Yes - -
References

https://zookeeper.apache.org/security.html#CVE-2019-0201
https://issues.apache.org/jira/browse/ZOOKEEPER-1392
http://www.securityfocus.com/bid/108427
https://lists.debian.org/debian-lts-announce/2019/05/msg00033.html
https://lists.apache.org/thread.html/f6112882e30a31992a79e0a8c31ac179e9d0de7c708de3a9258
https://lists.apache.org/thread.html/5d9a1cf41a5880557bf680b7321b4ab9a4d206c601ffb15fef6
https://www.debian.org/security/2019/dsa-4461
https://seclists.org/bugtraq/2019/Jun/13
https://security.netapp.com/advisory/ntap-20190619-0001/
https://lists.apache.org/thread.html/053d9ce4d579b02203db18545fee5e33f35f2932885459b74d1
https://access.redhat.com/errata/RHSA-2019:3140
https://lists.apache.org/thread.html/b0656d359c7d40ec9f39c8cc61bca66802ef9a2a12ee199f5b0
https://lists.apache.org/thread.html/519eb0fd45642dcecd9ff74cb3e71c20a4753f7d82e2f07864b
https://lists.apache.org/thread.html/f9bc3e55f4e28d1dcd1a69aae6d53e609a758e34d2869b4d798
https://access.redhat.com/errata/RHSA-2019:3892
https://access.redhat.com/errata/RHSA-2019:4352
https://www.oracle.com/security-alerts/cpujul2020.html
https://www.oracle.com/security-alerts/cpuoct2020.html
https://www.oracle.com//security-alerts/cpujul2021.html
https://lists.apache.org/thread.html/r40f32125c1d97ad82404cc918171d9e0fcf78e534256674e9d

CVE ID
CVE-2019-0201
Published
2019-05-23
Modified
2021-08-16
CVSSv2.0
Medium
CVSSv3.1
Medium
PCI Compliance
Fail
US-CERT Alert
No
CWE
CWE-862

Free Vulnerability Scanning, Assessment and Management

Mageni's Platform is packed with all the features you need to scan, assess and manage vulnerabilities like this - it is free, open source, lightning fast, reliable and scalable.

Router
Servers
Laptop
Database
Group
Cloud

Frequently Asked Questions

No, you can scan concurrently as many assets as you want. Please note that you must be aware of the hardware requeriments of the platform to ensure a good performance.

No, you can add as many assest as you want. It doesn't matters if you have millions of assets, we won't charge you for that.

No. The software is completely free. We have no intention to charge you to use the software, in fact - it completely goes against our beliefs and business model.

A vulnerability is defined in the ISO 27002 standard as “A weakness of an asset or group of assets that can be exploited by one or more threats” (International Organization for Standardization, 2005)

We generate revenue by providing support and other services for customers that require a subscription so they get guaranteed support and enterprise services. To use Mageni's Platform is completely free, with no limits at all.

Yes. Mageni understands that there are professionals and businesses that need commercial support so Mageni provides an active support subscription with everything needed to run Mageni's Platform reliably and securely. More than software, it's access to security experts, knowledge resources, security updates, and support tools you can't get anywhere else. The subscription includes:

  • Ongoing delivery
    • Patches
    • Bug fixes
    • Updates
    • Upgrades
  • Technical support
    • 24/7 availability
    • Unlimited Incidents
    • Specialty-based routing
    • Multi-Channel
  • Commitments
    • Software certifications
    • Software assurance
    • SLA

No, we don't store the information of your vulnerabilities in our servers.

Vulnerability management is the process in which vulnerabilities in IT are identified and the risks of these vulnerabilities are evaluated. This evaluation leads to correcting the vulnerabilities and removing the risk or a formal risk acceptance by the management of an organization. The term vulnerability management is often confused with vulnerability scanning. Despite the fact both are related, there is an important difference between the two. Vulnerability scanning consists of using a computer program to identify vulnerabilities in networks, computer infrastructure or applications. Vulnerability management is the process surrounding vulnerability scanning, also taking into account other aspects such as risk acceptance, remediation etc. Source: "Implementing a Vulnerability Management Process". SANS Institute.

I am ready to start scanning for vulnerabilities