This issue affects Kea versions 3.0.1 through 3.0.1 and 3.1.1 through 3.1.2.
Metrics
Affected Vendors & Products
No advisories yet.
Solution
Upgrade to the patched release most closely related to your current version of Kea: 3.0.2 or 3.1.3.
Workaround
Setting "hostname-char-replacement" to anything other than an empty value (suggestion: "x") is an effective workaround to this issue, regardless of other settings.
| Link | Providers |
|---|---|
| https://kb.isc.org/docs/cve-2025-11232 |
|
Wed, 29 Oct 2025 19:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Wed, 29 Oct 2025 18:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | To trigger the issue, three configuration parameters must have specific settings: "hostname-char-set" must be left at the default setting, which is "[^A-Za-z0-9.-]"; "hostname-char-replacement" must be empty (the default); and "ddns-qualifying-suffix" must *NOT* be empty (the default is empty). DDNS updates do not need to be enabled for this issue to manifest. A client that sends certain option content would then cause kea-dhcp4 to exit unexpectedly. This issue affects Kea versions 3.0.1 through 3.0.1 and 3.1.1 through 3.1.2. | |
| Title | Invalid characters cause assert | |
| Weaknesses | CWE-823 | |
| References |
| |
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: isc
Published:
Updated: 2025-10-29T18:22:23.455Z
Reserved: 2025-10-01T15:15:46.992Z
Link: CVE-2025-11232
Updated: 2025-10-29T18:22:14.126Z
Status : Received
Published: 2025-10-29T18:15:40.197
Modified: 2025-10-29T18:15:40.197
Link: CVE-2025-11232
No data.
OpenCVE Enrichment
No data.