# CVE-2025-32366: Information disclosure in ConnMan

> A remote attacker can trigger a buffer over-read in ConnMan's DNS proxy to leak stack memory contents over the network.

- **Severity:** Medium 4.8 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 5 Apr 2025
- **Updated:** 15 Apr 2025
- **Also known as:** DEBIAN-CVE-2025-32366, GHSA-9j63-jqr8-fh2v, UBUNTU-CVE-2025-32366

## What is CVE-2025-32366?

CVE-2025-32366 is a medium-severity vulnerability in ConnMan, published on 5 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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) without a check for whether the sum of *end and *rdlen exceeds max. Consequently, *rdlen may be larger than the amount of remaining packet data in the current state of parsing. Values of stack memory locations may be sent over the network in a response.

Weakness: CWE-130 (Improper Handling of Length Parameter Inconsistency)

## Which versions are affected by CVE-2025-32366?


## How do I fix CVE-2025-32366?

Apply the vendor's patch.

## Is CVE-2025-32366 being exploited?

There is no known exploitation of CVE-2025-32366 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-32366 and fix it if it is affected.

What it is: CVE-2025-32366 is a medium-severity vulnerability in ConnMan, published on 5 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-32366 in the wild and no public exploit code.

Affected product: ConnMan. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-32366/ (Markdown: https://insights.sbomify.com/CVE-2025-32366/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-32366
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-32366
- OSV: https://osv.dev/vulnerability/CVE-2025-32366

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-32366/
Summaries are generated and may contain mistakes; the official description above is the record.