Summary
[2.6.3-1]
- New version 2.6.3
- Fix for: CVE-2025-32801, CVE-2025-32802, CVE-2025-32803
- kea.conf: Remove /tmp/ from socket-name for existing configurations
- kea.conf: Set pseudo-random password for default config to secure fresh
install and allow CA startup without user intervention
- kea.conf: Restrict directory permissions
- Sync service files with upstream
- Fix leases ownership when switching from root to kea user
[2.6.1-9]
- Update location of fmf plans
[2.6.1-8]
- Properly check valgrind arches
[2.6.1-7]
- Use autoreconf more (fixes riscv64 build)
Fixed packages 5
| Release | Package | Fixed in |
|---|---|---|
| Oracle Linux · 10 | kea | 0:2.6.3-1.el10_0 |
| Oracle Linux · 10 | kea-doc | 0:2.6.3-1.el10_0 |
| Oracle Linux · 10 | kea-hooks | 0:2.6.3-1.el10_0 |
| Oracle Linux · 10 | kea-keama | 0:2.6.3-1.el10_0 |
| Oracle Linux · 10 | kea-libs | 0:2.6.3-1.el10_0 |
Vulnerabilities 3
-
High 7.8
Loading a malicious hook library can lead to local privilege escalation
Kea configuration and API directives can be used to load a malicious hook library. Many common configurations run Kea as root, leave the API entry points unsecured by default, and/or place the control sockets in insecure paths. This issue affects Kea versions…
-
Medium 6.1
Insecure handling of file paths allows multiple local attacks
Kea configuration and API directives can be used to overwrite arbitrary files, subject to permissions granted to Kea. Many common configurations run Kea as root, leave the API entry points unsecured by default, and/or place the control sockets in insecure pat…
-
Medium 4.0
Insecure file permissions can result in confidential information leakage
In some cases, Kea log files or lease files may be world-readable. This 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.