Skip to content

Apache ZooKeeper: Insufficient Permission Check in AdminServer Snapshot/Restore Commands

Moderate severity GitHub Reviewed Published Sep 24, 2025 to the GitHub Advisory Database • Updated Sep 26, 2025

Package

maven org.apache.zookeeper:zookeeper (Maven)

Affected versions

>= 3.9.0, < 3.9.4

Patched versions

3.9.4

Description

Improper permission checks in the AdminServer allow an authenticated client with insufficient privileges to invoke the snapshot and restore commands. The intended requirement is authentication and authorization on the root path (/) with ALL permission for these operations; however, affected versions permit invocation without that level of authorization. The primary risk is disclosure of cluster state via snapshots to a lesser-privileged client.

  • Affected: org.apache.zookeeper:zookeeper 3.9.0 through 3.9.3.
  • Fixed: 3.9.4 (ZOOKEEPER-4964 “check permissions individually during admin server auth”).
  • Mitigations:
    • Disable both commands (admin.snapshot.enabled, admin.restore.enabled).
    • Disable AdminServer (admin.enableServer).
    • Ensure the root ACL is not open; note that ZooKeeper ACLs are not recursive.
    • Upgrade to 3.9.4.

References

Published by the National Vulnerability Database Sep 24, 2025
Published to the GitHub Advisory Database Sep 24, 2025
Reviewed Sep 24, 2025
Last updated Sep 26, 2025

Severity

Moderate

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
Low
Integrity
None
Availability
None

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:L/I:N/A:N

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(21st percentile)

Weaknesses

Improper Handling of Insufficient Permissions or Privileges

The product does not handle or incorrectly handles when it has insufficient privileges to access resources or functionality as specified by their permissions. This may cause it to follow unexpected code paths that may leave the product in an invalid state. Learn more on MITRE.

CVE ID

CVE-2025-58457

GHSA ID

GHSA-2hmj-97jw-28jh

Source code

Credits

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