Service interruption via unthrottled HTTP requests
Published May 12, 2023 · Updated Jan 24, 2025
Resource exhaustion in Froxlor before 2.0.16 allows remote attackers to interrupt the service by flooding HTTP endpoints. Each session could send unlimited panel, API, or installer requests because those entry points performed no request-count check before processing. Network access to a deployed web interface is sufficient; sustained requests can exhaust server resources and interrupt availability.
Summary
What happened
Resource exhaustion in Froxlor before 2.0.16 allows remote attackers to interrupt the service by flooding HTTP endpoints. Each session could send unlimited panel, API, or installer requests because those entry points performed no request-count check before processing. Network access to a deployed web interface is sufficient; sustained requests can exhaust server resources and interrupt availability.
The record
- CVE
- CVE-2023-2666
- Published
- May 12, 2023
- Updated
- Jan 24, 2025
- Vendor
- Froxlor
- Product
- Froxlor
- Classifications
- CWE-770, T1499.003
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 12, 2023CVE publishedPublication date reported by the CVE source.
- Jan 24, 2025Record 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=unspecified <2.0.16
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