ConnMan up to 1.44 dnsproxy.c parse_rr RDLENGTH length parameter

Summaryinfo

A vulnerability marked as problematic has been reported in ConnMan up to 1.44. This affects the function parse_rr of the file dnsproxy.c. Performing a manipulation of the argument RDLENGTH results in length parameter. This vulnerability is identified as CVE-2025-32366. The attack can be initiated remotely. There is not any exploit available. To fix this issue, it is recommended to deploy a patch.

Detailsinfo

A vulnerability was found in ConnMan up to 1.44. It has been classified as problematic. This affects the function parse_rr of the file dnsproxy.c. The manipulation of the argument RDLENGTH with an unknown input leads to a length parameter vulnerability. CWE is classifying the issue as CWE-130. The product parses a formatted message or structure, but it does not handle or incorrectly handles a length field that is inconsistent with the actual length of the associated data. This is going to have an impact on availability. The summary by CVE is:

In ConnMan through 1.44, parse_rr in dnsproxy.c has a memcpy length that depends on an RR RDLENGTH value, i.e., *rdlen=ntohs(rr->rdlen) and memcpy(response+offset,*end,*rdlen).

It is possible to read the advisory at web.git.kernel.org. This vulnerability is uniquely identified as CVE-2025-32366 since 04/05/2025. The exploitability is told to be difficult. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details of the vulnerability are known, but there is no available exploit.

Applying a patch is able to eliminate this problem. The bugfix is ready for download at web.git.kernel.org.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Name

• ConnMan

Version

• 1.0
• 1.1
• 1.2
• 1.3
• 1.4
• 1.5
• 1.6
• 1.7
• 1.8
• 1.9
• 1.10
• 1.11
• 1.12
• 1.13
• 1.14
• 1.15
• 1.16
• 1.17
• 1.18
• 1.19
• 1.20
• 1.21
• 1.22
• 1.23
• 1.24
• 1.25
• 1.26
• 1.27
• 1.28
• 1.29
• 1.30
• 1.31
• 1.32
• 1.33
• 1.34
• 1.35
• 1.36
• 1.37
• 1.38
• 1.39
• 1.40
• 1.41
• 1.42
• 1.43
• 1.44

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion