# OpenStack Compute (Nova) Folsom before 2012.2.2 and Grizzly, when using libvirt and LVM backed instances, does not properly clear physical volume (PV) content when reallocating for instances, which...

Advisory record · `PYSEC-2012-41` · Withdrawn

- **Identifiers:** `PYSEC-2012-41` · `CVE-2012-5625`
- **State:** Withdrawn
- **Severity:** CVSS 6.5 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-212](https://cwe.mitre.org/data/definitions/212.html)
- **Tags:** [CWE-212](https://agentprime.io/advisories/tag/cwe-212.md)
- **Published:** 26 Dec 2012
- **Updated:** 21 May 2026
- **Reviewed by a person:** No

**Withdrawn.** OSV withdrew this advisory on 22 Nov 2024. The record stays here, marked withdrawn.

Published by OSV at 26 Dec 2012, 22:55 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `nova` (PyPI): affected `<a99a802e008eed18e39fc1d98170edc495cbd354 || all versions`; fixed in `a99a802e008eed18e39fc1d98170edc495cbd354`

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 6.5 Medium, CVSS 3.1: `CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N`, from CNA (redhat)

- **CISA KEV:** Not listed.
- **EPSS:** 0.013, the 71st percentile, on 6 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

This record came from the full history of OSV, published 26 Dec 2012. New records show when each source confirmed them.

## Sources

- [OSV: PYSEC-2012-41](https://osv.dev/vulnerability/PYSEC-2012-41)
- <https://github.com/openstack/nova/commit/a99a802e008eed18e39fc1d98170edc495cbd354>
- <http://www.ubuntu.com/usn/USN-1663-1>
- <https://github.com/openstack/nova/commit/9d2ea970422591f8cdc394001be9a2deca499a5f>
- <https://launchpad.net/nova/folsom/2012.2.2>
- <http://osvdb.org/88419>
- <http://www.openwall.com/lists/oss-security/2012/12/11/5>
- <https://bugs.launchpad.net/nova/+bug/1070539>
- <http://rhn.redhat.com/errata/RHSA-2013-0208.html>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/PYSEC-2012-41>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/PYSEC-2012-41/>. Everything for agents: <https://agentprime.io/llms.txt>.