Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-11232: CWE-823 Use of Out-of-range Pointer Offset in ISC Kea

0
High
VulnerabilityCVE-2025-11232cvecve-2025-11232cwe-823
Published: Wed Oct 29 2025 (10/29/2025, 18:02:39 UTC)
Source: CVE Database V5
Vendor/Project: ISC
Product: Kea

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.

AI-Powered Analysis

AILast updated: 11/05/2025, 19:24:45 UTC

Technical Analysis

CVE-2025-11232 is a vulnerability classified under CWE-823 (Use of Out-of-range Pointer Offset) affecting ISC Kea DHCP server versions 3.0.1 and 3.1.1. The flaw arises when three configuration parameters are set in a specific manner: the "hostname-char-set" remains at its default regex value "[^A-Za-z0-9.-]", "hostname-char-replacement" is left empty, and "ddns-qualifying-suffix" is set to a non-empty string. Under these conditions, a specially crafted DHCP client request containing certain option content can trigger an out-of-bounds pointer dereference in the kea-dhcp4 process, causing it to exit unexpectedly. This results in a denial-of-service (DoS) condition by crashing the DHCP server process. Notably, Dynamic DNS (DDNS) updates do not need to be enabled for the vulnerability to manifest. The vulnerability can be exploited remotely without requiring any privileges or user interaction, increasing its risk profile. Although no public exploits have been reported yet, the CVSS v3.1 score of 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) indicates a high severity focused on availability impact. The root cause is improper bounds checking leading to an out-of-range pointer offset during processing of DHCP options under the specified configuration. This vulnerability could disrupt DHCP services, impacting IP address assignment and network connectivity for clients relying on affected servers.

Potential Impact

For European organizations, the primary impact of CVE-2025-11232 is denial of service against DHCP infrastructure. DHCP servers running vulnerable Kea versions may crash upon receiving malicious DHCP requests, causing loss of IP address assignment services. This can lead to widespread network outages, affecting enterprise operations, critical infrastructure, and public services dependent on reliable network connectivity. The lack of authentication or user interaction requirements means attackers can remotely trigger the crash, potentially from within or outside the network perimeter. Organizations with large-scale deployments of ISC Kea in data centers, ISPs, or government networks could experience significant operational disruption. Additionally, the downtime may increase exposure to secondary attacks due to loss of network controls. Although no confidentiality or integrity impact is indicated, the availability impact alone can have severe consequences for business continuity and service delivery in sectors such as finance, healthcare, telecommunications, and public administration across Europe.

Mitigation Recommendations

To mitigate CVE-2025-11232, organizations should first verify if their Kea DHCP servers are running affected versions 3.0.1 or 3.1.1. Immediate mitigation can be achieved by modifying configuration parameters to avoid the vulnerable state: specifically, ensure that either "hostname-char-set" is changed from its default, "hostname-char-replacement" is set to a non-empty value, or "ddns-qualifying-suffix" remains empty. This configuration change prevents the out-of-range pointer offset from being triggered. Organizations should monitor ISC advisories and apply official patches or upgrades as soon as they become available. Network-level protections such as DHCP request filtering or rate limiting can reduce exposure to malicious DHCP packets. Implementing robust network segmentation and monitoring DHCP server logs for abnormal crashes or restarts can aid in early detection. Regular backups and failover DHCP servers can minimize downtime impact. Finally, conducting internal penetration testing to simulate exploit attempts can validate the effectiveness of mitigations.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.2
Assigner Short Name
isc
Date Reserved
2025-10-01T15:15:46.992Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 6902598f52c03fa7b6eb66e0

Added to database: 10/29/2025, 6:14:39 PM

Last enriched: 11/5/2025, 7:24:45 PM

Last updated: 12/13/2025, 9:43:39 PM

Views: 111

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats