# CVE-2022-24863: Denial of service in http-swagger

> An attacker can cause memory exhaustion and denial of service in http-swagger by exploiting improper handling of HTTP methods.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Apr 2022
- **Updated:** 23 Apr 2025

## What is CVE-2022-24863?

CVE-2022-24863 is a high-severity denial of service vulnerability in swaggo http-swagger, published on 18 Apr 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

http-swagger is an open source wrapper to automatically generate RESTful API documentation with Swagger 2.0. In versions of http-swagger prior to 1.2.6 an attacker may perform a denial of service attack consisting of memory exhaustion on the host system. The cause of the memory exhaustion is down to improper handling of http methods. Users are advised to upgrade. Users unable to upgrade may to restrict the path prefix to the "GET" method as a workaround.

Weakness: CWE-755 (Improper Handling of Exceptional Conditions), CWE-400 (Uncontrolled Resource Consumption)

## Which versions are affected by CVE-2022-24863?

It affects 1 product.


Products: Http-Swagger Project Http-Swagger.

## How do I fix CVE-2022-24863?

Upgrade to a fixed version.

## Is CVE-2022-24863 being exploited?

There is no known exploitation of CVE-2022-24863 in the wild and no public exploit code.

## Other vulnerabilities in swaggo http-swagger

- [CVE-2024-25712](https://insights.sbomify.com/CVE-2024-25712/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-24863 and fix it if it is affected.

What it is: CVE-2022-24863 is a high-severity denial of service vulnerability in swaggo http-swagger, published on 18 Apr 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-24863 in the wild and no public exploit code.

Affected product: swaggo http-swagger. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-24863/ (Markdown: https://insights.sbomify.com/CVE-2022-24863/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-24863
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-24863
- OSV: https://osv.dev/vulnerability/CVE-2022-24863

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-24863/
Summaries are generated and may contain mistakes; the official description above is the record.