ghsa-6h7w-fc84-x7p6
Vulnerability from github
Published
2021-05-28 15:54
Modified
2021-05-27 21:17
Summary
StaticFile.fromUrl can leak presence of a directory
Details

Impact

StaticFile.fromUrl can leak the presence of a directory on a server when the URL scheme is not file://, and the URL points to a fetchable resource under its scheme and authority. The function returns F[None], indicating no resource, if url.getFile is a directory, without first checking the scheme or authority of the URL. If a URL connection to the scheme and URL would return a stream, and the path in the URL exists as a directory on the server, the presence of the directory on the server could be inferred from the 404 response. The contents and other metadata about the directory are not exposed.

This affects http4s versions: * 0.21.7 through 0.21.23 * 0.22.0-M1 through 0.22.0-M8 * 0.23.0-M1 * 1.0.0-M1 through 1.0.0-M22

Patches

The patch is available in the following versions:

  • v0.21.24
  • v0.22.0-RC1
  • v0.23.0-RC1
  • v1.0.0-M23

Note: a previous version of this advisory incorrectly referred to 0.22.0-M9 and 0.23.0-M2.

Workarounds

Don't call StaticFile.fromUrl with non-file URLs.

For more information

If you have any questions or comments about this advisory: * Open an issue in the http4s repository * Disclose further vulnerabilities according to the http4s security policy

Show details on source website


{
  "affected": [
    {
      "package": {
        "ecosystem": "Maven",
        "name": "org.http4s:http4s-core"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0.21.7"
            },
            {
              "fixed": "0.21.24"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "database_specific": {
        "last_known_affected_version_range": "\u003c= 0.22.0-M8"
      },
      "package": {
        "ecosystem": "Maven",
        "name": "org.http4s:http4s-core"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0.22.0-M1"
            },
            {
              "fixed": "0.22.0-RC1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "package": {
        "ecosystem": "Maven",
        "name": "org.http4s:http4s-core"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0.23.0-M1"
            },
            {
              "fixed": "0.23.0-RC1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "0.23.0-M1"
      ]
    },
    {
      "database_specific": {
        "last_known_affected_version_range": "\u003c= 1.0.0-M22"
      },
      "package": {
        "ecosystem": "Maven",
        "name": "org.http4s:http4s-core"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "1.0.0-M1"
            },
            {
              "fixed": "1.0.0-M23"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2021-32643"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-22"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2021-05-27T21:17:06Z",
    "nvd_published_at": "2021-05-27T18:15:00Z",
    "severity": "MODERATE"
  },
  "details": "### Impact\n\n`StaticFile.fromUrl` can leak the presence of a directory on a server when the `URL` scheme is not `file://`, and the URL points to a fetchable resource under its scheme and authority.  The function returns `F[None]`, indicating no resource, if `url.getFile` is a directory, without first checking the scheme or authority of the URL.  If a URL connection to the scheme and URL would return a stream, and the path in the URL exists as a directory on the server, the presence of the directory on the server could be inferred from the 404 response.  The contents and other metadata about the directory are not exposed.\n\nThis affects http4s versions:\n* 0.21.7 through 0.21.23\n* 0.22.0-M1 through 0.22.0-M8\n* 0.23.0-M1\n* 1.0.0-M1 through 1.0.0-M22\n\n### Patches\n\nThe [patch](https://github.com/http4s/http4s/commit/52e1890665410b4385e37b96bc49c5e3c708e4e9) is available in the following versions:\n\n* v0.21.24\n* v0.22.0-RC1\n* v0.23.0-RC1\n* v1.0.0-M23\n\nNote: a previous version of this advisory incorrectly referred to 0.22.0-M9 and 0.23.0-M2.\n\n### Workarounds\n\nDon\u0027t call `StaticFile.fromUrl` with non-file URLs.\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n* Open an issue in [the http4s repository](https://github.com/http4s/http4s)\n* Disclose further vulnerabilities according to the [http4s security policy](https://github.com/http4s/http4s/blob/main/SECURITY.md)\n",
  "id": "GHSA-6h7w-fc84-x7p6",
  "modified": "2021-05-27T21:17:06Z",
  "published": "2021-05-28T15:54:39Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/http4s/http4s/security/advisories/GHSA-6h7w-fc84-x7p6"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2021-32643"
    },
    {
      "type": "WEB",
      "url": "https://github.com/http4s/http4s/commit/52e1890665410b4385e37b96bc49c5e3c708e4e9"
    },
    {
      "type": "WEB",
      "url": "https://mvnrepository.com/artifact/org.http4s/http4s-core"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N",
      "type": "CVSS_V3"
    }
  ],
  "summary": "StaticFile.fromUrl can leak presence of a directory"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.


Loading…