Summary
OpenStack Neutron Improper Input Validation vulnerability
OpenStack Neutron before 2014.2.4 (juno) and 2015.1.x before 2015.1.1 (kilo), when using the IPTables firewall driver, allows remote authenticated users to cause a denial of service (L2 agent crash) by adding an address pair that is rejected by the ipset tool.
Impact
The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths. Typical impact: varies by context: data corruption, logic bypass, or denial of service.
Affected versions
Security releases
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 environmentNew to Kodem? Get a demo →Remediation advice
neutron to 2014.2.4 or later; neutron to 2015.1.1 or later
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2015-3221? CVE-2015-3221 is a medium-severity improper input validation vulnerability in neutron (pip), affecting versions < 2014.2.4. It is fixed in 2014.2.4, 2015.1.1. The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths.
- Which versions of neutron are affected by CVE-2015-3221? neutron (pip) versions < 2014.2.4 is affected.
- Is there a fix for CVE-2015-3221? Yes. CVE-2015-3221 is fixed in 2014.2.4, 2015.1.1. Upgrade to this version or later.
- Is CVE-2015-3221 exploitable, and should I be worried? Whether CVE-2015-3221 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-3221 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-3221?
- Upgrade
neutronto 2014.2.4 or later - Upgrade
neutronto 2015.1.1 or later
- Upgrade