Skip to content

← Public intelligence

Go package

github.com/swaggo/http-swagger

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

2 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Medium, CVSS 6.1GoPublished

    http-swagger XSS via PUT requests

    CVE-2024-25712 · GHSA-49w7-5r33-jm9m

    Affected
    • Go github.com/swaggo/http-swagger < 1.2.6
    Fixed in
    1.2.6· Vendor fix available
    Issue
    http-swagger before 1.2.6 allows XSS via PUT requests, because a file that has been uploaded (via httpSwagger.WrapHandler and webdav.memFile) can subsequently be accessed via a GET request. NOTE: this is independently fixable with respect to CVE-2022-24863, because (if a solution continued to allow PUT requests) large files could have been blocked without blocking JavaScript, or JavaScript could have been blocked without blocking large files.

    Recommended action: Upgrade to 1.2.6 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  2. High, CVSS 7.5GoPublished

    Denial of Service in http-swagger

    CVE-2022-24863 · GHSA-xg75-q3q5-cqmv

    Affected
    • Go github.com/swaggo/http-swagger < 1.2.6
    Fixed in
    1.2.6· Vendor fix available
    Issue
    Impact Allows an attacker to perform a DOS attack consisting of memory exhaustion on the host system. Patches Yes. Please upgrade to v1.2.6. Workarounds A workaround is to restrict the path prefix to the "GET" method. As shown below References Reporter dongguangli from https://www.huoxian.cn/ company For more information If you have any questions or comments about this advisory: Open an issue in http-swagger

    Recommended action: Upgrade to 1.2.6 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →