x/vulndb: potential Go vuln in github.com/swaggo/http-swagger: CVE-2022-24863

[GoVulnBot]

CVE-2022-24863 references github.com/swaggo/http-swagger, which may be a Go module.

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.

Links:

• NIST: https://nvd.nist.gov/vuln/detail/CVE-2022-24863
• JSON: https://github.com/CVEProject/cvelist/tree/d855890b7ea7f5cef27af49e2e13bc246faecb39/2022/24xxx/CVE-2022-24863.json
• Commit: swaggo/http-swagger@b7d83e8
• PR: fix: security improvement swaggo/http-swagger#62
• https://github.com/swaggo/http-swagger/releases/tag/v1.2.6
• GHSA-xg75-q3q5-cqmv

See doc/triage.md for instructions on how to triage this report.

module: github.com/swaggo/http-swagger
package: http-swagger
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.

cves:
  - CVE-2022-24863
links:
    pr: https://github.com/swaggo/http-swagger/pull/62
    commit: https://github.com/swaggo/http-swagger/commit/b7d83e8fba85a7a51aa7e45e8244b4173f15049e
    context:
      - https://github.com/swaggo/http-swagger/releases/tag/v1.2.6
      - https://github.com/swaggo/http-swagger/security/advisories/GHSA-xg75-q3q5-cqmv

[neild]

I do not understand how this is a vulnerability.

This package provides an HTTP handler. The linked PR changes that handler to reject any request method other than GET. However, I don't see how attacker-caused memory exhaustion can occur from permitting other methods. The usual cause of such memory exhaustion would be unbounded buffering of the request body, but the HTTP handler never reads the request body and net/http doesn't do unbounded buffering.

[neild]

#2547 explained the problem in much better detail. There is indeed a vulnerability here. Reopening.

[gopherbot]

Change https://go.dev/cl/568015 mentions this issue: data/reports: add GO-2022-0427.yaml