pysec-2024-188
Vulnerability from pysec
Published
2024-08-14 21:15
Modified
2025-01-19 04:23
Details

WebOb provides objects for HTTP requests and responses. When WebOb normalizes the HTTP Location header to include the request hostname, it does so by parsing the URL that the user is to be redirected to with Python's urlparse, and joining it to the base URL. urlparse however treats a // at the start of a string as a URI without a scheme, and then treats the next part as the hostname. urljoin will then use that hostname from the second part as the hostname replacing the original one from the request. This vulnerability is patched in WebOb version 1.8.8.




{
  "affected": [
    {
      "package": {
        "ecosystem": "PyPI",
        "name": "webob",
        "purl": "pkg:pypi/webob"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "f689bcf4f0a1f64f1735b1d5069aef5be6974b5b"
            }
          ],
          "repo": "https://github.com/pylons/webob",
          "type": "GIT"
        },
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "1.8.8"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "0.8",
        "0.8.1",
        "0.8.2",
        "0.8.3",
        "0.8.4",
        "0.8.5",
        "0.9",
        "0.9.1",
        "0.9.2",
        "0.9.3",
        "0.9.4",
        "0.9.5",
        "0.9.6",
        "0.9.6.1",
        "0.9.7",
        "0.9.7.1",
        "0.9.8",
        "1.0",
        "1.0.1",
        "1.0.2",
        "1.0.3",
        "1.0.4",
        "1.0.5",
        "1.0.6",
        "1.0.7",
        "1.0.8",
        "1.1",
        "1.1.1",
        "1.1b2",
        "1.1beta1",
        "1.1rc1",
        "1.2",
        "1.2.1",
        "1.2.2",
        "1.2.3",
        "1.2b1",
        "1.2b2",
        "1.2b3",
        "1.2rc1",
        "1.3",
        "1.3.1",
        "1.4",
        "1.4.1",
        "1.4.2",
        "1.5.0",
        "1.5.0a0",
        "1.5.0a1",
        "1.5.0b0",
        "1.5.1",
        "1.6.0",
        "1.6.0a0",
        "1.6.1",
        "1.6.2",
        "1.6.3",
        "1.6.4",
        "1.7.0",
        "1.7.0rc1",
        "1.7.0rc2",
        "1.7.1",
        "1.7.2",
        "1.7.3",
        "1.7.4",
        "1.8.0",
        "1.8.0rc1",
        "1.8.1",
        "1.8.2",
        "1.8.3",
        "1.8.4",
        "1.8.5",
        "1.8.6",
        "1.8.7"
      ]
    }
  ],
  "aliases": [
    "CVE-2024-42353",
    "GHSA-mg3v-6m49-jhp3"
  ],
  "details": "WebOb provides objects for HTTP requests and responses. When WebOb normalizes the HTTP Location header to include the request hostname, it does so by parsing the URL that the user is to be redirected to with Python\u0027s urlparse, and joining it to the base URL. `urlparse` however treats a `//` at the start of a string as a URI without a scheme, and then treats the next part as the hostname. `urljoin` will then use that hostname from the second part as the hostname replacing the original one from the request. This vulnerability is patched in WebOb version 1.8.8.",
  "id": "PYSEC-2024-188",
  "modified": "2025-01-19T04:23:01.908824+00:00",
  "published": "2024-08-14T21:15:17+00:00",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://github.com/Pylons/webob/security/advisories/GHSA-mg3v-6m49-jhp3"
    },
    {
      "type": "EVIDENCE",
      "url": "https://github.com/Pylons/webob/security/advisories/GHSA-mg3v-6m49-jhp3"
    },
    {
      "type": "FIX",
      "url": "https://github.com/Pylons/webob/commit/f689bcf4f0a1f64f1735b1d5069aef5be6974b5b"
    }
  ],
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N",
      "type": "CVSS_V3"
    }
  ]
}


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.