# CVE-2016-7498: Denial of service in n/a

> Remote authenticated users can cause disk consumption denial of service by deleting instances during resize operations in OpenStack Compute.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **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:** 27 Sep 2016
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2016-7498, GHSA-47vm-xhwp-2v86

## What is CVE-2016-7498?

CVE-2016-7498 is a medium-severity denial of service vulnerability in n/a, published on 27 Sep 2016. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

OpenStack Compute (nova) 13.0.0 does not properly delete instances from compute nodes, which allows remote authenticated users to cause a denial of service (disk consumption) by deleting instances while in the resize state.  NOTE: this vulnerability exists because of a CVE-2015-3280 regression.

Weakness: CWE-399

## Which versions are affected by CVE-2016-7498?

It affects 1 product.


Products: Openstack Compute \(Nova\).

## How do I fix CVE-2016-7498?

Apply the vendor's patch.

## Is CVE-2016-7498 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-7498 and fix it if it is affected.

What it is: CVE-2016-7498 is a medium-severity denial of service vulnerability in n/a, published on 27 Sep 2016. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2016-7498 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-2016-7498/ (Markdown: https://insights.sbomify.com/CVE-2016-7498/index.md)
```

## Sources

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

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