Host memory exhaustion via unrestricted HTTP methods
Published Apr 18, 2022 · Updated Apr 23, 2025
Uncontrolled resource consumption in Swaggo http-swagger before 1.2.6 allows remote attackers to exhaust host memory through HTTP requests. The Handler accepts non-GET methods and passes them to a WebDAV handler backed by an in-memory filesystem, where PUT requests store attacker-controlled files without an effective resource bound. No authentication or user interaction is required, and repeated uploads can consume the hosting process memory until its service is interrupted.
Summary
What happened
Uncontrolled resource consumption in Swaggo http-swagger before 1.2.6 allows remote attackers to exhaust host memory through HTTP requests. The Handler accepts non-GET methods and passes them to a WebDAV handler backed by an in-memory filesystem, where PUT requests store attacker-controlled files without an effective resource bound. No authentication or user interaction is required, and repeated uploads can consume the hosting process memory until its service is interrupted.
The record
- CVE
- CVE-2022-24863
- Published
- Apr 18, 2022
- Updated
- Apr 23, 2025
- Vendor
- Swaggo
- Product
- http-swagger
- Classifications
- CWE-755, CWE-400, T1499.003
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 18, 2022CVE publishedPublication date reported by the CVE source.
- Apr 23, 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=< 1.2.6
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