Skip to main content
Vulnerability Database/CVE-2025-32803

CVE-2025-32803: Kea DHCP Server Information Disclosure Flaw

CVE-2025-32803 is an information disclosure vulnerability in Kea DHCP Server where log and lease files may be world-readable, exposing sensitive network data. This post covers the technical details, affected versions, and mitigation steps.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2025-32803 Overview

CVE-2025-32803 is an incorrect default permissions vulnerability [CWE-276] in ISC Kea, the open-source DHCP server from the Internet Systems Consortium (ISC). Under certain conditions, Kea creates log files or lease files with world-readable permissions. Local users on the system can read DHCP lease databases and server logs that should remain restricted.

The issue affects Kea versions 2.4.0 through 2.4.1, 2.6.0 through 2.6.2, and 2.7.0 through 2.7.8. Exploitation requires local access, and impact is limited to confidentiality of DHCP operational data.

Critical Impact

Local users can read Kea DHCP lease files and log data, exposing network topology information, MAC addresses, IP assignments, and client identifiers.

Affected Products

  • ISC Kea DHCP Server 2.4.0 through 2.4.1
  • ISC Kea DHCP Server 2.6.0 through 2.6.2
  • ISC Kea DHCP Server 2.7.0 through 2.7.8

Discovery Timeline

  • 2025-05-28 - CVE CVE-2025-32803 published to NVD
  • 2026-06-17 - Last updated in NVD database

Technical Details for CVE-2025-32803

Vulnerability Analysis

The vulnerability stems from Kea assigning overly permissive file system permissions when creating log files and lease files. These files may be created world-readable, allowing any local user account to read them without additional privileges.

Kea lease files store active DHCP lease state, including client MAC addresses, assigned IP addresses, hostnames, client identifiers, and lease timing data. Log files capture DHCP transaction records and operational diagnostics. Exposure of these artifacts provides local attackers with network reconnaissance data useful for lateral movement or targeted attacks against specific hosts.

The vulnerability does not permit modification of lease data or disruption of DHCP service availability. Impact is confined to confidentiality.

Root Cause

The root cause is incorrect default permission handling [CWE-276] during file creation. Depending on deployment configuration and umask, Kea may create or recreate these files with modes that grant read access to all local accounts rather than restricting access to the service account and administrators.

Attack Vector

Exploitation requires an authenticated local account on the host running Kea. No elevated privileges, user interaction, or network access are required. An attacker with shell access reads the files directly from their configured paths, typically under /var/lib/kea/ for lease data and /var/log/kea/ or syslog destinations for logs.

Review the ISC CVE-2025-32803 Documentation for file paths, affected configurations, and vendor guidance.

Detection Methods for CVE-2025-32803

Indicators of Compromise

  • Kea lease files (for example, kea-leases4.csv, kea-leases6.csv) with world-readable mode bits set (-rw-r--r-- or broader).
  • Kea log files under /var/log/kea/ or custom log paths with permissions granting read access to the other class.
  • Unexpected access timestamps on lease or log files that do not correlate with service activity or administrator sessions.

Detection Strategies

  • Audit file permissions on all configured Kea lease and log paths using stat or find /var/lib/kea /var/log/kea -perm -o=r.
  • Enable Linux audit rules (auditd) to log open and openat syscalls against Kea data files by non-root, non-service accounts.
  • Review Kea configuration files for log destinations and verify permissions after each service restart or log rotation event.

Monitoring Recommendations

  • Alert on reads of Kea lease and log files by user accounts other than the configured Kea service user or root.
  • Monitor package upgrades and configuration deployments that may recreate files with incorrect modes.
  • Track log rotation operations to confirm post-rotation files retain restrictive permissions.

How to Mitigate CVE-2025-32803

Immediate Actions Required

  • Upgrade ISC Kea to a fixed release as documented in the ISC CVE-2025-32803 Documentation.
  • Immediately restrict permissions on existing lease and log files using chmod 640 and set ownership to the Kea service account.
  • Inventory all hosts running Kea 2.4.x, 2.6.x, and 2.7.x and prioritize multi-tenant or shared systems for remediation.

Patch Information

ISC has published remediation guidance for CVE-2025-32803. Consult the ISC CVE-2025-32803 Documentation for the fixed version numbers corresponding to the 2.4, 2.6, and 2.7 branches, and apply vendor packages or build updated binaries from source.

Workarounds

  • Set a restrictive umask (for example, 027) in the Kea service unit or init script so new files are created without world-readable permissions.
  • Apply chmod 640 and chown kea:kea to existing lease and log files, and enforce the same mode through logrotate create directives.
  • Restrict directory permissions on /var/lib/kea and /var/log/kea to 0750 to prevent directory traversal by unprivileged users.
bash
# Configuration example
# Restrict existing Kea lease and log file permissions
sudo chown -R kea:kea /var/lib/kea /var/log/kea
sudo chmod 750 /var/lib/kea /var/log/kea
sudo find /var/lib/kea /var/log/kea -type f -exec chmod 640 {} \;

# Enforce restrictive umask in the systemd unit
# /etc/systemd/system/kea-dhcp4.service.d/override.conf
[Service]
UMask=0027

# Enforce mode on rotated logs
# /etc/logrotate.d/kea
/var/log/kea/*.log {
    weekly
    rotate 8
    compress
    missingok
    notifempty
    create 0640 kea kea
}

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.