How severe is CVE-2015-3221?

No CVSS score has been assigned to CVE-2015-3221 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2015-3221?

CVE-2015-3221 affects the following packages: neutron (PyPI), neutron (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2015-3221?

Update neutron to 2014.2.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2015-3221 is resolved across your whole dependency graph.

How do I detect CVE-2015-3221 in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for neutron, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2015-3221 if there is no patch (or I can't update yet)?

Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Is CVE-2015-3221 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2015-3221, including 1 documented proof-of-concept exploit on Exploit-DB. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2015-3221?

CVE-2015-3221 has an EPSS (Exploit Prediction Scoring System) score of 11.4%, placing it in the 96th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score warrants monitoring and prompt remediation.

What type of vulnerability is CVE-2015-3221?

CVE-2015-3221 is classified as Improper Input Validation (CWE-20). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2015-3221 published, and has it been updated?

CVE-2015-3221 was published on August 26, 2015 and was last updated on July 7, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍 PyPI

Not in CISA KEV

CVE-2015-3221 — neutron

CVE-2015-3221 is a Improper Input Validation vulnerability in neutron. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for neutron — see the affected versions and patch details below.

OpenStack Neutron Improper Input Validation vulnerability

Also known asGHSA-wf44-4mgj-rwvxPYSEC-2026-856

Published

Aug 26, 2015

Updated

Jul 7, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

1 known

Exploitation data as of Nov 1, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

11.4%probability of exploitation in next 30 days

Moderate Risk0.00%

Lower risk than most CVEs96th percentile — riskier than 96% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

2 pkgs affected

🐍neutron🐍neutron

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`neutron`	≥ 2000&&< 2014.2.4	2014.2.4`pip install --upgrade 'neutron==2014.2.4'`
🐍PyPI	`neutron`	≥ 2015.1.0&&< 2015.1.1	2015.1.1`pip install --upgrade 'neutron==2015.1.1'`

Affected Products

1 product · 2 configurations

Application

neutronopenstack

≥ 2015.1.0 && < 2015.1.1

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-37360webappsphp

GeniXCMS 0.0.3 - Cross-Site Scripting

by hyp3rlinx · Jun 24, 2015

Exploit-DB Source

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for neutron, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update neutron to 2014.2.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2015-3221 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

Product	Fixed in	Advisory
Red Hat Enterprise Linux OpenStack Platform 6.0 (Juno) for RHEL 7	`openstack-neutron-0:2014.2.3-9.el7ost`	RHSA-2015:1680

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2015-3221 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works