# CVE-2014-3657: Denial of service in n/a

> Remote attackers can cause a denial of service via deadlock in libvirt by sending a NULL parameter to the virConnectListAllDomains API.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 6 Oct 2014
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2014-3657, GHSA-543q-9rm2-x5f3, UBUNTU-CVE-2014-3657

## What is CVE-2014-3657?

CVE-2014-3657 is a medium-severity denial of service vulnerability in n/a, published on 6 Oct 2014. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The virDomainListPopulate function in conf/domain_conf.c in libvirt before 1.2.9 does not clean up the lock on the list of domains, which allows remote attackers to cause a denial of service (deadlock) via a NULL value in the second parameter in the virConnectListAllDomains API command.

Weakness: CWE-399

## Which versions are affected by CVE-2014-3657?

It affects 1 product.


Products: Libvirt Libvirt.

## How do I fix CVE-2014-3657?

Upgrade to a fixed version.

## Is CVE-2014-3657 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2008-5086](https://insights.sbomify.com/CVE-2008-5086/): Missing authorization in n/a (high 7.2)
- [CVE-2015-5160](https://insights.sbomify.com/CVE-2015-5160/): Information disclosure in n/a (medium 5.5)
- [CVE-2010-2237](https://insights.sbomify.com/CVE-2010-2237/): Information disclosure in n/a (medium 4.4)
- [CVE-2010-2238](https://insights.sbomify.com/CVE-2010-2238/): Path traversal in n/a (medium 4.4)
- [CVE-2010-2239](https://insights.sbomify.com/CVE-2010-2239/): Information disclosure in n/a (medium 4.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-3657 and fix it if it is affected.

What it is: CVE-2014-3657 is a medium-severity denial of service vulnerability in n/a, published on 6 Oct 2014. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2014-3657 in the wild and no public exploit code.

Affected product: n/a. 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-2014-3657/ (Markdown: https://insights.sbomify.com/CVE-2014-3657/index.md)
```

## Sources

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

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