OpenStack Neutron up to 2014.2.3/2015.1.0 IPTables Firewall Driver input validation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.9 | $0-$5k | 0.00 |
Summary
A vulnerability marked as problematic has been reported in OpenStack Neutron up to 2014.2.3/2015.1.0. Impacted is an unknown function of the component IPTables Firewall Driver. Performing a manipulation results in input validation. This vulnerability is known as CVE-2015-3221. Furthermore, an exploit is available. It is suggested to upgrade the affected component.
Details
A vulnerability classified as problematic has been found in OpenStack Neutron up to 2014.2.3/2015.1.0 (Cloud Software). This affects an unknown code of the component IPTables Firewall Driver. The manipulation with an unknown input leads to a input validation vulnerability. CWE is classifying the issue as CWE-20. The product receives input or data, but it does
not validate or incorrectly validates that the input has the
properties that are required to process the data safely and
correctly. This is going to have an impact on availability. The summary by CVE is:
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.
The weakness was published 08/26/2015 (Website). The advisory is shared at bugs.launchpad.net. This vulnerability is uniquely identified as CVE-2015-3221 since 04/10/2015. It is possible to initiate the attack remotely. A authentication is needed for exploitation. Technical details are unknown but a public exploit is available.
The exploit is shared for download at exploit-db.com. It is declared as proof-of-concept.
Upgrading to version 2014.2.4 or 2015.1.1 eliminates this vulnerability.
The vulnerability is also documented in the databases at Exploit-DB (37360), SecurityFocus (BID 75368†) and Vulnerability Center (SBV-54121†). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.3VulDB Meta Temp Score: 3.9
VulDB Base Score: 4.3
VulDB Temp Score: 3.9
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Input validationCWE: CWE-20
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Exploit-DB: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: OpenStack Neutron 2014.2.4/2015.1.1
Timeline
04/10/2015 🔍06/23/2015 🔍
08/26/2015 🔍
08/26/2015 🔍
08/27/2015 🔍
11/03/2015 🔍
01/20/2025 🔍
Sources
Advisory: RHSA-2015:1680Status: Confirmed
Confirmation: 🔍
CVE: CVE-2015-3221 (🔍)
GCVE (CVE): GCVE-0-2015-3221
GCVE (VulDB): GCVE-100-77445
SecurityFocus: 75368
Vulnerability Center: 54121 - OpenStack Neutron Remote DoS Vulnerability by Adding an Address Pair That is Rejected by the Ipset Tool, Medium
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 08/27/2015 11:15Updated: 01/20/2025 16:00
Changes: 08/27/2015 11:15 (48), 03/10/2018 10:55 (8), 06/13/2022 14:22 (3), 01/20/2025 16:00 (25)
Complete: 🔍
Cache ID: 216:617:103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.