Unauthenticated service interruption via resource-intensive updates
Published Jun 1, 2020 · Updated Aug 6, 2024
Uncontrolled resource consumption in Lexiglot through 2014-11-20 allows remote attackers to interrupt service through the update API. The api/update.php endpoint launches a Subversion update operation whose execution consumes substantial server resources. Unauthenticated network access is sufficient, and repeated requests exhaust resources without reported data disclosure or modification.
Summary
What happened
Uncontrolled resource consumption in Lexiglot through 2014-11-20 allows remote attackers to interrupt service through the update API. The api/update.php endpoint launches a Subversion update operation whose execution consumes substantial server resources. Unauthenticated network access is sufficient, and repeated requests exhaust resources without reported data disclosure or modification.
The record
- CVE
- CVE-2014-8937
- Published
- Jun 1, 2020
- Updated
- Aug 6, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-400, T1499.003
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 1, 2020CVE publishedPublication date reported by the CVE source.
- Aug 6, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
- JAHx181 Lexiglot denial-of-service proof of conceptproof of concept · unverified
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