OpenStack Ironic up to 21.4.3/23.0.2/24.1.2/26.0.x URL image_source stack-based overflow
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in OpenStack Ironic up to 21.4.3/23.0.2/24.1.2/26.0.x and classified as critical. This issue affects the function image_source of the component URL Handler. Performing a manipulation results in stack-based overflow.
This vulnerability is identified as CVE-2024-47211. There is not any exploit available.
The affected component should be upgraded.
Details
A vulnerability classified as critical has been found in OpenStack Ironic up to 21.4.3/23.0.2/24.1.2/26.0.x. This affects the function image_source of the component URL Handler. The manipulation with an unknown input leads to a stack-based overflow vulnerability. CWE is classifying the issue as CWE-121. A stack-based buffer overflow condition is a condition where the buffer being overwritten is allocated on the stack (i.e., is a local variable or, rarely, a parameter to a function). This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
In OpenStack Ironic before 21.4.4, 22.x and 23.x before 23.0.3, 23.x and 24.x before 24.1.3, and 25.x and 26.x before 26.1.0, there is a lack of checksum validation of supplied image_source URLs when configured to convert images to a raw format for streaming.
The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2024-47211 since 09/21/2024. The exploitability is told to be easy. Technical details are known, but no exploit is available.
The vulnerability scanner Nessus provides a plugin with the ID 214503 (RHEL 9 : Red Hat OpenStack Platform 18.0.4 (openstack-ironic) (RHSA-2025:0439)), which helps to determine the existence of the flaw in a target environment.
Upgrading to version 21.4.4, 23.0.3, 24.1.3 or 26.1.0 eliminates this vulnerability. The upgrade is hosted for download at github.com.
The vulnerability is also documented in the vulnerability database at Tenable (214503). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
License
Website
- Vendor: https://www.openstack.org/
- Product: https://github.com/openstack/ironic/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.5VulDB Meta Temp Score: 5.3
VulDB Base Score: 5.5
VulDB Temp Score: 5.3
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: 🔍
Exploiting
Class: Stack-based overflowCWE: CWE-121 / CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Partially
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 214503
Nessus Name: RHEL 9 : Red Hat OpenStack Platform 18.0.4 (openstack-ironic) (RHSA-2025:0439)
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Ironic 21.4.4/23.0.3/24.1.3/26.1.0
Timeline
09/21/2024 🔍10/04/2024 🔍
10/04/2024 🔍
01/23/2025 🔍
Sources
Vendor: openstack.orgProduct: github.com
Advisory: github.com
Status: Confirmed
CVE: CVE-2024-47211 (🔍)
GCVE (CVE): GCVE-0-2024-47211
GCVE (VulDB): GCVE-100-279261
Entry
Created: 10/04/2024 20:37Updated: 01/23/2025 00:04
Changes: 10/04/2024 20:37 (58), 10/08/2024 04:05 (1), 01/23/2025 00:04 (2)
Complete: 🔍
Cache ID: 216::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.