Unauthorized cluster-tag binding via missing ownership check
Published May 22, 2023 · Updated Oct 9, 2024
Incorrect authorization in Apache InLong 1.2.0 through 1.6.0 allows remote attackers to bind cluster tags to clusters they do not own. InlongClusterServiceImpl.bindTag updates clusterTags for caller-supplied cluster IDs without checking the operator against each cluster's inCharges owners. Network access to InLong Manager is sufficient under the published assessment, and exploitation changes cluster-to-tag associations without disclosing data or interrupting service.
Summary
What happened
Incorrect authorization in Apache InLong 1.2.0 through 1.6.0 allows remote attackers to bind cluster tags to clusters they do not own. InlongClusterServiceImpl.bindTag updates clusterTags for caller-supplied cluster IDs without checking the operator against each cluster's inCharges owners. Network access to InLong Manager is sufficient under the published assessment, and exploitation changes cluster-to-tag associations without disclosing data or interrupting service.
The record
- CVE
- CVE-2023-31454
- Published
- May 22, 2023
- Updated
- Oct 9, 2024
- Vendor
- The Apache Software Foundation
- Product
- Apache InLong
- Classifications
- CWE-732, T1565.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 22, 2023CVE publishedPublication date reported by the CVE source.
- Oct 9, 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=1.2.0 <=1.6.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