What is CVE-2015-3280?

CVE-2015-3280 is a medium-severity security vulnerability in nova (pip), affecting versions < 2014.2.4. It is fixed in 2014.2.4, 2015.1.2.

Which versions of nova are affected by CVE-2015-3280?

nova (pip) versions < 2014.2.4 is affected.

Is there a fix for CVE-2015-3280?

Yes. CVE-2015-3280 is fixed in 2014.2.4, 2015.1.2. Upgrade to this version or later.

Is CVE-2015-3280 exploitable, and should I be worried?

Whether CVE-2015-3280 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2015-3280 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2015-3280?

Upgrade: nova to 2014.2.4 or later, nova to 2015.1.2 or later.

CVE-2015-3280 in nova

Q: Which versions of nova are affected by CVE-2015-3280?

nova (pip) versions < 2014.2.4 is affected.

Q: Is there a fix for CVE-2015-3280?

Yes. CVE-2015-3280 is fixed in 2014.2.4, 2015.1.2. Upgrade to this version or later.

Q: Is CVE-2015-3280 exploitable, and should I be worried?

Whether CVE-2015-3280 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2015-3280 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2015-3280?

Upgrade: nova to 2014.2.4 or later, nova to 2015.1.2 or later.

Summary

OpenStack Compute (nova) allows remote authenticated users to cause a denial of service

OpenStack Compute (nova) before 2014.2.4 (juno) and 2015.1.x before 2015.1.2 (kilo) 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.

Impact

Affected versions

nova (< 2014.2.4) nova (>= 2015.1.0, < 2015.1.2)

Security releases

nova → 2014.2.4 (pip) nova → 2015.1.2 (pip)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade the following packages to resolve this vulnerability:

nova to 2014.2.4 or later; nova to 2015.1.2 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2015-3280? CVE-2015-3280 is a medium-severity security vulnerability in nova (pip), affecting versions < 2014.2.4. It is fixed in 2014.2.4, 2015.1.2.
Which versions of nova are affected by CVE-2015-3280? nova (pip) versions < 2014.2.4 is affected.
Is there a fix for CVE-2015-3280? Yes. CVE-2015-3280 is fixed in 2014.2.4, 2015.1.2. Upgrade to this version or later.
Is CVE-2015-3280 exploitable, and should I be worried? Whether CVE-2015-3280 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2015-3280 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2015-3280?
- Upgrade nova to 2014.2.4 or later
- Upgrade nova to 2015.1.2 or later

Other vulnerabilities in nova

CVE-IDSeverityPackage summary

CVE-2026-46448Mediumnova: OpenStack Nova: Nova scheduler hint injection bypasses Placement resource claims and scheduling constraints CVE-2026-24708HighNova: OpenStack Nova calls qemu-img without format restrictions for resize CVE-2024-40767MediumNova: OpenStack Nova vulnerable to unauthorized access to potentially sensitive data CVE-2024-32498Highcinder: OpenStack Cinder, Glance, and Nova vulnerable to arbitrary file access CVE-2022-47951Mediumcinder: OpenStack Cinder, glance, and Nova vulnerable to Path Traversal