MEDIUM 6.3

CVE-2025-70102: dhcpcd 10.3.0 NULL Pointer Dereference Denial of Service

dhcpcd 10.3.0 contains a crash vulnerability triggered when parsing malformed or unexpected configuration options. The vulnerable code attempts to access properties of a data structure without first verifying it exists, causing the application to crash. This affects systems that use dhcpcd for DHCP configuration, particularly in automated environments or where untrusted configuration input is processed.

Source data · NVD / CISA · public domain

CVSS
3.1 · 6.3 MEDIUM · CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
Weaknesses (CWE)
CWE-476
Affected products
0 configuration(s)
Published / Modified
2026-06-15 / 2026-06-17

NVD description (verbatim)

A NULL pointer dereference occurs in Roy Marples NetworkConfiguration/dhcpcd 10.3.0 while parsing configuration options. In parse_option() (src/if-options.c:1886), the code performs a member access on a NULL pointer of type 'struct dhcp_opt' when an unexpected/invalid option token or parsing state causes the lookup to yield NULL. The instrumented fuzzing build reports 'runtime error: member access within null pointer of type struct dhcp_opt' and aborts.

1 reference(s) · View on NVD →

SEC.co analysis · AI-assisted, reviewed against source

Technical summary

A NULL pointer dereference vulnerability exists in the parse_option() function at src/if-options.c:1886 in dhcpcd 10.3.0. During configuration option parsing, a lookup operation on an option token can return NULL under certain conditions—such as receipt of an unexpected or invalid option token, or an invalid parsing state. The vulnerable code proceeds to dereference this NULL pointer as a 'struct dhcp_opt' without null-checking, triggering a crash. Fuzzing instrumentation confirms the vulnerability manifests as 'runtime error: member access within null pointer of type struct dhcp_opt'.

Business impact

The primary impact is denial of service: affected systems running dhcpcd will crash when exposed to specially crafted or malformed configuration options, temporarily disrupting DHCP-dependent network functionality. In environments where dhcpcd is critical to network boot, container initialization, or automatic IP configuration, such crashes can disrupt service availability. While not a remote code execution risk, the crash can be leveraged for disruption attacks or as a vector for follow-on attacks when combined with system restart delays.

Affected systems

Roy Marples NetworkConfiguration dhcpcd version 10.3.0 is confirmed vulnerable. Systems running dhcpcd for DHCP configuration—including Linux systems, embedded devices, virtualization hosts, and containers relying on dynamic IP assignment—are affected if they process untrusted configuration input or accept configuration from potentially malicious sources.

Exploitability

The vulnerability requires delivery of a crafted configuration option string to the affected parse_option() function. Exploitability depends on the attack surface: if dhcpcd processes configuration files or options from untrusted sources (local unprivileged users, network-accessible config services, or adversary-supplied DHCP messages with embedded options), the barrier to triggering the crash is low. The attack does not require special privileges or user interaction, though it does require access to configuration input mechanisms. Remote exploitation is possible if the system accepts malicious DHCP option payloads.

Remediation

Upgrade dhcpcd to a version that includes a null-pointer check before dereferencing the option structure returned by the lookup operation. Verify the patched version against Roy Marples' official releases and security advisories. As an interim mitigation, restrict configuration input sources and disable DHCP option parsing features if not required for your deployment.

Patch guidance

Check Roy Marples' official dhcpcd repository and security advisories for version 10.3.1 or later, which should include a fix for this NULL pointer dereference. Verify the patch against the vendor advisory to confirm the specific version number. Test patched versions in a non-production environment before deploying broadly, particularly on systems where DHCP is critical to network initialization.

Detection guidance

Monitor system logs for dhcpcd process crashes or unexpected terminations, particularly in correlation with configuration reloads or DHCP message events. If running instrumented or debug builds, watch for runtime errors mentioning 'member access within null pointer of type struct dhcp_opt'. Check for suspicious or malformed DHCP option payloads in network traffic or configuration file changes. Correlate crash timestamps with any configuration pushes or untrusted DHCP server activity.

Why prioritize this

Although scored as MEDIUM severity (CVSS 6.3), this vulnerability should be prioritized for systems where dhcpcd is critical to service availability or where untrusted configuration input is a realistic threat. Denial-of-service vulnerabilities in foundational network services can cascade to affect dependent applications and infrastructure. Systems in environments accepting configuration from partially-trusted sources (multi-tenant hosts, edge devices, or those processing remote config updates) warrant faster remediation.

Risk score, explained

CVSS 3.1 score of 6.3 reflects a vulnerability with local or adjacent network attack vector (AV:A), low attack complexity (AC:L), no privilege requirement (PR:N), and no user interaction needed (UI:N). The impact is bounded—confidentiality, integrity, and availability are each lowered but not fully compromised. This is a denial-of-service issue rather than a data breach or privilege escalation, hence the MEDIUM rating rather than HIGH.

Frequently asked questions

Can this vulnerability be exploited remotely?

Exploitability depends on your environment. If dhcpcd is configured to process DHCP options from untrusted networks or if configuration files are pushed from remote sources, remote exploitation is possible. In purely local scenarios where configuration is tightly controlled, the attack surface is narrower. Assess your configuration ingestion mechanisms to determine remote risk.

Does this affect all dhcpcd installations?

Version 10.3.0 is confirmed vulnerable. Older versions may also be affected; check vendor advisories for the range of vulnerable versions. Systems running newer patched versions are not at risk. If you are unsure of your version, run 'dhcpcd --version' to confirm.

What is the difference between this vulnerability and a code execution flaw?

This is a crash (denial of service), not code execution. An attacker triggers dhcpcd to crash by sending malformed configuration, disrupting network services but not gaining shell access or data exfiltration capabilities. However, repeated crashes or crash-induced system instability can be used as part of a broader attack strategy.

Should we apply this patch immediately?

If dhcpcd is central to your infrastructure and you process configuration from partially-trusted sources, patch promptly after testing. If dhcpcd is used in a controlled environment with strictly curated configuration, the risk is lower but patching is still recommended. Do not delay testing due to the MEDIUM rating; denial-of-service flaws in critical network services warrant timely remediation.

This analysis is provided for informational purposes to assist security professionals in understanding and remediating CVE-2025-70102. SEC.co does not guarantee the accuracy of inferences beyond the source data provided and recommends verification against official vendor advisories and security bulletins. Exploit or proof-of-concept code is not provided. Organizations should conduct their own risk assessment and testing in their environment before applying patches or making configuration changes. No liability is assumed for decisions or actions taken based on this analysis. Source: NVD (public-domain), retrieved 2026-07-23. Analysis generated by SEC.co (claude-haiku-4-5).