Cross-tenant tag modification via incorrect policy identifier
Published Nov 24, 2024 · Updated Jan 6, 2025
Authorization bypass in OpenStack Neutron allows remote authenticated users to alter network tags on resources owned by other tenants. In neutron/extensions/tagging.py, the tag controller uses an incorrect resource identifier for policy enforcement, so ownership is checked against the wrong object before tag changes. An unprivileged tenant account is sufficient to add or clear another tenant's network tags in 23.0.0 through 23.2.0, 24.0.0 through 24.0.1, and 25.0.0.
Summary
What happened
Authorization bypass in OpenStack Neutron allows remote authenticated users to alter network tags on resources owned by other tenants. In neutron/extensions/tagging.py, the tag controller uses an incorrect resource identifier for policy enforcement, so ownership is checked against the wrong object before tag changes. An unprivileged tenant account is sufficient to add or clear another tenant's network tags in 23.0.0 through 23.2.0, 24.0.0 through 24.0.1, and 25.0.0.
The record
- CVE
- CVE-2024-53916
- Published
- Nov 24, 2024
- Updated
- Jan 6, 2025
- Vendor
- OpenStack
- Product
- Neutron
- Classifications
- CWE-754, T1565.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 24, 2024CVE publishedPublication date reported by the CVE source.
- Jan 6, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=25.0.0
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo