API crash via unhandled asynchronous request errors
Published Dec 13, 2023 · Updated Oct 8, 2024
Improper input validation in Cube Core before 0.34.34 allows remote authenticated users to crash the Cube API with a crafted request. API gateway asynchronous handlers did not forward rejected promises to the global Express error middleware, leaving request-triggered errors unhandled. A low-privileged API credential and a request that triggers an asynchronous handler rejection are sufficient to interrupt the entire API service.
Summary
What happened
Improper input validation in Cube Core before 0.34.34 allows remote authenticated users to crash the Cube API with a crafted request. API gateway asynchronous handlers did not forward rejected promises to the global Express error middleware, leaving request-triggered errors unhandled. A low-privileged API credential and a request that triggers an asynchronous handler rejection are sufficient to interrupt the entire API service.
The record
- CVE
- CVE-2023-50709
- Published
- Dec 13, 2023
- Updated
- Oct 8, 2024
- Vendor
- Cube Dev
- Product
- Cube Core
- Classifications
- CWE-20, T1499
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 13, 2023CVE publishedPublication date reported by the CVE source.
- Oct 8, 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=< 0.34.34
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