BSD Ports

ISC KEA -- Invalid characters cause assert

· CVE-2025-11232 · VuXML entry

Internet Systems Consortium, Inc. reports: 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 …

Affected versions

By system

0 still vulnerable, 3 fixed. Where VuXML applies (FreeBSD, DragonFly, FreeBSD's derivatives) a port is vulnerable while its version is in a range; pkgsrc says itself whether it lists a CVE of this advisory; OpenBSD and MidnightBSD keep no list this site reads, so their row is only an estimate: FreeBSD's ranges applied to upstream's version.

SystemPortVersionStateFixed
DragonFlynet/kea2.6.3 fixed
OpenBSDnet/kea3.2.1 out of range, by version
NetBSDnet/kea3.1.9nb2 not listed
MidnightBSDnet/kea3.0.2_1 out of range, by version
FreeBSDnet/kea3.2.1_1 fixed (337 days after)
FreeBSDnet/kea-devel3.3.2_1 fixed (271 days after)