Arbitrary File Overwrite Vulnerability in Kea Package
Summary
ALPINE-CVE-2025-32802: Kea configuration and API directives can be used to overwrite arbitrary files, subject to permissions granted to Kea. Affects kea versions < 2.6.3-r0. Fixed in 2.6.3-r0. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
Kea is a dynamic host configuration protocol (DHCP) server that provides network configuration to devices on a network. It is designed to be flexible and scalable, catering to various network environments. However, certain configurations can expose the server to security risks, particularly when run with elevated privileges or with unsecured API endpoints.
Vulnerability Detail
The vulnerability allows attackers to overwrite arbitrary files on the system where Kea is running, depending on the permissions granted to the Kea process. This issue arises from insecure configurations that often run Kea as root and leave API entry points unsecured. The affected versions include Kea 2.4.0 through 2.4.1, 2.6.0 through 2.6.2, and 2.7.0 through 2.7.8. If exploited, this vulnerability could lead to unauthorized access and manipulation of critical system files.
How To Fix
Minimum fixed version
2.6.3-r0
This is the first release that contains the fix.
sudo apk add --upgrade keaTip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →
Workaround
As a temporary workaround, you can restrict the permissions of the control sockets and ensure that the API endpoints are secured. This can be done by modifying the configuration file to specify secure paths and limiting access to trusted users only.
Conclusion
The Kea package has a significant vulnerability that allows for arbitrary file overwriting due to insecure configurations. It is crucial to update to the patched version and implement security best practices to safeguard your system.
See every vulnerability recorded for kea →
FAQ
Kea versions 2.4.0 through 2.4.1, 2.6.0 through 2.6.2, and 2.7.0 through 2.7.8 are affected.
The CVSS score of this vulnerability is 6.1, indicating a medium severity level.
You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without requiring any signup.
Exploitation of this vulnerability could lead to unauthorized access to system files, potentially compromising the integrity and security of the entire system.
Yes, ensure that you do not run Kea as root, secure API entry points, and place control sockets in secure paths to mitigate risks.
References
Related vulnerabilities
Recent vulnerabilities recorded for kea.
