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-12198: Heap-based Buffer Overflow in dnsmasq

0
High
VulnerabilityCVE-2025-12198cvecve-2025-12198
Published: Mon Oct 27 2025 (10/27/2025, 00:58:12 UTC)
Source: CVE Database V5
Product: dnsmasq

Description

A vulnerability has been found in dnsmasq up to 2.73rc6. Affected is the function parse_hex of the file src/util.c of the component Config File Handler. The manipulation of the argument i leads to heap-based buffer overflow. Local access is required to approach this attack. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

AI-Powered Analysis

AILast updated: 10/27/2025, 01:36:38 UTC

Technical Analysis

CVE-2025-12198 is a heap-based buffer overflow vulnerability identified in the widely used DNS forwarder and DHCP server software dnsmasq, affecting versions up to 2.73rc6. The flaw resides in the parse_hex function within the src/util.c file, part of the configuration file handler component. Specifically, improper manipulation of the argument 'i' during parsing leads to a heap overflow condition. This vulnerability requires local access with low privileges, meaning an attacker must have some level of access to the target system but does not require elevated rights or user interaction. The overflow can corrupt heap memory, potentially allowing an attacker to execute arbitrary code, escalate privileges, or cause denial of service by crashing the service. The CVSS 4.0 score of 8.5 reflects the high impact on confidentiality, integrity, and availability, combined with the relatively low attack complexity and privileges required. The vulnerability was publicly disclosed on October 27, 2025, with exploit code available, but no confirmed exploitation in the wild has been reported. The vendor has not responded to the disclosure, and no official patches have been released, increasing the urgency for organizations to implement mitigations. Given dnsmasq's role in network infrastructure, exploitation could disrupt DNS and DHCP services, impacting network reliability and security.

Potential Impact

For European organizations, this vulnerability poses significant risks, especially for those relying on dnsmasq in network infrastructure, including ISPs, enterprises, and government agencies. Successful exploitation could allow local attackers to escalate privileges, gain unauthorized access to sensitive network configurations, or disrupt critical DNS and DHCP services, leading to network outages or data breaches. The impact on confidentiality is high due to potential unauthorized access, integrity is compromised through possible code execution or configuration manipulation, and availability is threatened by service crashes or denial of service. The requirement for local access limits remote exploitation but does not eliminate risk, as insider threats or compromised accounts could leverage this flaw. The lack of vendor response and patches increases exposure time, making timely mitigation critical. Disruption of DNS/DHCP services can have cascading effects on business operations, especially in sectors like finance, healthcare, and critical infrastructure prevalent in Europe.

Mitigation Recommendations

Immediate mitigation should focus on restricting local access to systems running vulnerable dnsmasq versions by enforcing strict access controls and monitoring for suspicious local activity. Network segmentation can limit exposure of affected hosts. Administrators should audit and inventory dnsmasq versions in use and prioritize upgrading to patched versions once available. In the absence of official patches, organizations can consider applying community-developed patches or backporting fixes from future releases. Employing runtime protections such as heap memory protection mechanisms (e.g., ASLR, heap canaries) can reduce exploitation success. Regularly monitoring logs for abnormal dnsmasq behavior or crashes can provide early detection. Additionally, implementing multi-factor authentication and minimizing the number of users with local access reduces the attack surface. Organizations should also prepare incident response plans for potential exploitation scenarios involving dnsmasq.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
VulDB
Date Reserved
2025-10-25T06:21:53.115Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 68fec91d23a7bbed3245769f

Added to database: 10/27/2025, 1:21:33 AM

Last enriched: 10/27/2025, 1:36:38 AM

Last updated: 10/28/2025, 2:57:11 AM

Views: 13

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