Cross-project resource modification via unchecked identifiers
Published Dec 28, 2023 · Updated Sep 9, 2024
Authorization bypass in FIT2CLOUD MeterSphere before 2.10.10-lts allows remote authenticated users to modify other projects' resources. Published sources do not identify the affected endpoint or function, but the operation accepts a known resource identifier without enforcing project ownership. A valid account and another project's resource identifier are required, and the documented consequence is limited to unauthorized resource changes.
Summary
What happened
Authorization bypass in FIT2CLOUD MeterSphere before 2.10.10-lts allows remote authenticated users to modify other projects' resources. Published sources do not identify the affected endpoint or function, but the operation accepts a known resource identifier without enforcing project ownership. A valid account and another project's resource identifier are required, and the documented consequence is limited to unauthorized resource changes.
The record
- CVE
- CVE-2023-50267
- Published
- Dec 28, 2023
- Updated
- Sep 9, 2024
- Vendor
- FIT2CLOUD
- Product
- MeterSphere
- Classifications
- CWE-639, CWE-269
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 28, 2023CVE publishedPublication date reported by the CVE source.
- Sep 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=< 2.10.10-lts
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