CVE-2024-53916: n/a
In OpenStack Neutron before 25.0.1, neutron/extensions/tagging.py can use an incorrect ID during policy enforcement. It does not apply the proper policy check for changing network tags. An unprivileged tenant is able to change (add and clear) tags on network objects that do not belong to the tenant, and this action is not subjected to the proper policy authorization check. This affects 23 before 23.2.1, 24 before 24.0.2, and 25 before 25.0.1.
AI Analysis
Technical Summary
CVE-2024-53916 is a vulnerability identified in OpenStack Neutron, specifically in the tagging.py extension module responsible for managing network object tags. In versions before 25.0.1 (including 23 before 23.2.1 and 24 before 24.0.2), the policy enforcement mechanism incorrectly uses an ID that does not correspond to the tenant owning the network object. This results in the failure to apply proper authorization checks when tenants attempt to add or clear tags on network resources. Consequently, an unprivileged tenant can manipulate tags on network objects belonging to other tenants without triggering the intended policy restrictions. Tags in OpenStack Neutron are metadata elements that can influence network management, automation, and policy enforcement. Unauthorized tag changes can lead to misconfiguration, misattribution of resources, or bypassing of network controls. The vulnerability does not require authentication or user interaction, making it remotely exploitable over the network. The CVSS 3.1 score of 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N) indicates a high impact on integrity with no confidentiality or availability impact. No public exploits are currently known, but the flaw is significant due to the broad scope of affected versions and the critical role of Neutron in OpenStack cloud networking.
Potential Impact
The primary impact of CVE-2024-53916 is the unauthorized modification of network tags by unprivileged tenants, which compromises the integrity of network metadata. This can lead to several adverse effects for organizations: misconfiguration of network policies, incorrect resource attribution, and potential circumvention of network segmentation or access controls that rely on tags. Such unauthorized changes could disrupt automated workflows, monitoring, and billing processes that depend on accurate tagging. Although confidentiality and availability are not directly affected, the integrity compromise can indirectly facilitate further attacks or operational errors. Organizations running multi-tenant OpenStack clouds are particularly at risk, as malicious tenants could manipulate network tags to interfere with other tenants’ resources, undermining trust and cloud isolation. This vulnerability could also impact compliance with security policies and regulatory requirements related to cloud resource management.
Mitigation Recommendations
To mitigate CVE-2024-53916, organizations should upgrade OpenStack Neutron to version 25.0.1 or later, or apply backported patches if available for earlier supported releases (23.2.1 and 24.0.2 or newer). Until patched, administrators should restrict tenant permissions to limit tag modification capabilities, possibly disabling tagging features for untrusted tenants. Implementing enhanced monitoring and alerting for unusual tag changes can help detect exploitation attempts. Reviewing and tightening policy definitions related to network tagging in Neutron can reduce risk. Additionally, segregating tenants with strict network isolation and minimizing shared infrastructure can limit the impact of unauthorized tag modifications. Regular audits of network tags and associated policies will help identify inconsistencies caused by potential exploitation. Finally, keeping OpenStack components updated and following vendor security advisories is essential for ongoing protection.
Affected Countries
United States, Germany, United Kingdom, France, Japan, Canada, Australia, India, China, South Korea, Brazil, Netherlands, Singapore
CVE-2024-53916: n/a
Description
In OpenStack Neutron before 25.0.1, neutron/extensions/tagging.py can use an incorrect ID during policy enforcement. It does not apply the proper policy check for changing network tags. An unprivileged tenant is able to change (add and clear) tags on network objects that do not belong to the tenant, and this action is not subjected to the proper policy authorization check. This affects 23 before 23.2.1, 24 before 24.0.2, and 25 before 25.0.1.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2024-53916 is a vulnerability identified in OpenStack Neutron, specifically in the tagging.py extension module responsible for managing network object tags. In versions before 25.0.1 (including 23 before 23.2.1 and 24 before 24.0.2), the policy enforcement mechanism incorrectly uses an ID that does not correspond to the tenant owning the network object. This results in the failure to apply proper authorization checks when tenants attempt to add or clear tags on network resources. Consequently, an unprivileged tenant can manipulate tags on network objects belonging to other tenants without triggering the intended policy restrictions. Tags in OpenStack Neutron are metadata elements that can influence network management, automation, and policy enforcement. Unauthorized tag changes can lead to misconfiguration, misattribution of resources, or bypassing of network controls. The vulnerability does not require authentication or user interaction, making it remotely exploitable over the network. The CVSS 3.1 score of 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N) indicates a high impact on integrity with no confidentiality or availability impact. No public exploits are currently known, but the flaw is significant due to the broad scope of affected versions and the critical role of Neutron in OpenStack cloud networking.
Potential Impact
The primary impact of CVE-2024-53916 is the unauthorized modification of network tags by unprivileged tenants, which compromises the integrity of network metadata. This can lead to several adverse effects for organizations: misconfiguration of network policies, incorrect resource attribution, and potential circumvention of network segmentation or access controls that rely on tags. Such unauthorized changes could disrupt automated workflows, monitoring, and billing processes that depend on accurate tagging. Although confidentiality and availability are not directly affected, the integrity compromise can indirectly facilitate further attacks or operational errors. Organizations running multi-tenant OpenStack clouds are particularly at risk, as malicious tenants could manipulate network tags to interfere with other tenants’ resources, undermining trust and cloud isolation. This vulnerability could also impact compliance with security policies and regulatory requirements related to cloud resource management.
Mitigation Recommendations
To mitigate CVE-2024-53916, organizations should upgrade OpenStack Neutron to version 25.0.1 or later, or apply backported patches if available for earlier supported releases (23.2.1 and 24.0.2 or newer). Until patched, administrators should restrict tenant permissions to limit tag modification capabilities, possibly disabling tagging features for untrusted tenants. Implementing enhanced monitoring and alerting for unusual tag changes can help detect exploitation attempts. Reviewing and tightening policy definitions related to network tagging in Neutron can reduce risk. Additionally, segregating tenants with strict network isolation and minimizing shared infrastructure can limit the impact of unauthorized tag modifications. Regular audits of network tags and associated policies will help identify inconsistencies caused by potential exploitation. Finally, keeping OpenStack components updated and following vendor security advisories is essential for ongoing protection.
Technical Details
- Data Version
- 5.1
- Assigner Short Name
- mitre
- Date Reserved
- 2024-11-24T00:00:00.000Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 699f6bc2b7ef31ef0b55ab74
Added to database: 2/25/2026, 9:38:10 PM
Last enriched: 2/28/2026, 3:18:19 AM
Last updated: 4/12/2026, 8:49:45 AM
Views: 17
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.