Authenticated metadata tampering via missing ownership context
Published Sep 6, 2022 · Updated Aug 3, 2024
Incorrect authorization in OpenStack Barbican before 14.0.0 allows remote authenticated users to alter any secret's metadata. The secret-metadata controllers supplied generic ACL context without the owning project's ID and secret creator, so legacy policy rules could not enforce ownership. A valid Barbican account is required; unauthorized metadata changes can corrupt protected data or consume protected resources until the service is denied.
Summary
What happened
Incorrect authorization in OpenStack Barbican before 14.0.0 allows remote authenticated users to alter any secret's metadata. The secret-metadata controllers supplied generic ACL context without the owning project's ID and secret creator, so legacy policy rules could not enforce ownership. A valid Barbican account is required; unauthorized metadata changes can corrupt protected data or consume protected resources until the service is denied.
The record
- CVE
- CVE-2022-23451
- Published
- Sep 6, 2022
- Updated
- Aug 3, 2024
- Vendor
- OpenStack
- Product
- Barbican
- Classifications
- CWE-863, T1565.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 6, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=Fixed in v14.0.0
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.
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