# CVE-2025-32743: Memory corruption in ConnMan

> Attackers can crash ConnMan or execute arbitrary code via malformed DNS responses with truncated bits, affecting Linux network management.

- **Severity:** Critical 9.0 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Apr 2025
- **Updated:** 10 Apr 2025
- **Also known as:** DEBIAN-CVE-2025-32743, GHSA-r8hx-vf7j-v5q3, UBUNTU-CVE-2025-32743

## What is CVE-2025-32743?

CVE-2025-32743 is a critical memory corruption vulnerability in ConnMan, published on 10 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, the lookup string in ns_resolv in dnsproxy.c can be NULL or an empty string when the TC (Truncated) bit is set in a DNS response. This allows attackers to cause a denial of service (application crash) or possibly execute arbitrary code, because those lookup values lead to incorrect length calculations and incorrect memcpy operations.

Weakness: CWE-392 (Missing Report of Error Condition)

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


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

Apply the vendor's patch.

## Is CVE-2025-32743 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-32743 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2025-32743 is a critical memory corruption vulnerability in ConnMan, published on 10 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-32743 exists.

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-32743/ (Markdown: https://insights.sbomify.com/CVE-2025-32743/index.md)
```

## Sources

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

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