Authenticated service crash via unbounded request-body reads
Published Jan 3, 2024 · Updated Aug 27, 2024
Resource exhaustion in CubeFS ObjectNode before 3.3.1 allows remote authenticated users to crash the service via oversized HTTP bodies. Affected S3 handlers read entire request bodies into memory with ioutil.ReadAll without first enforcing an upper size boundary. Exploitation requires credentials with object-delete permission and the name of an existing bucket; one request can exhaust host memory and deny storage access to other users.
Summary
What happened
Resource exhaustion in CubeFS ObjectNode before 3.3.1 allows remote authenticated users to crash the service via oversized HTTP bodies. Affected S3 handlers read entire request bodies into memory with ioutil.ReadAll without first enforcing an upper size boundary. Exploitation requires credentials with object-delete permission and the name of an existing bucket; one request can exhaust host memory and deny storage access to other users.
The record
- CVE
- CVE-2023-46738
- Published
- Jan 3, 2024
- Updated
- Aug 27, 2024
- Vendor
- CubeFS
- Product
- CubeFS
- Classifications
- CWE-770, T1499
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 3, 2024CVE publishedPublication date reported by the CVE source.
- Aug 27, 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=< 3.3.1
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