Unrelated access-rule deletion via faulty name lookup
Published Nov 17, 2024 · Updated Dec 5, 2024
Improper access-rule deletion in Red Hat OpenStack Platform allows remote authenticated users to delete unrelated rules through its CLI. The access rule delete command uses generic resource lookup code that wrongly assumes access rules have a name, so a missing ID can resolve to a different rule. Exploitation requires valid OpenStack credentials and an attempted deletion of a nonexistent ID; the result can alter authorization data and interrupt dependent access.
Summary
What happened
Improper access-rule deletion in Red Hat OpenStack Platform allows remote authenticated users to delete unrelated rules through its CLI. The access rule delete command uses generic resource lookup code that wrongly assumes access rules have a name, so a missing ID can resolve to a different rule. Exploitation requires valid OpenStack credentials and an attempted deletion of a nonexistent ID; the result can alter authorization data and interrupt dependent access.
The record
- CVE
- CVE-2023-6110
- Published
- Nov 17, 2024
- Updated
- Dec 5, 2024
- Vendor
- Red Hat
- Product
- Red Hat OpenStack Platform
- Classifications
- CWE-237, T1531
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 17, 2024CVE publishedPublication date reported by the CVE source.
- Dec 5, 2024Record 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?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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