ghsa-4mmh-5vw7-rgvj
Vulnerability from github
Published
2022-08-18 19:07
Modified
2022-08-18 19:07
Summary
Venice vulnerable to Partial Path Traversal issue within the functions `load-file` and `load-resource`
Details

Impact

A partial path traversal issue exists within the functions load-file and load-resource. These functions can be limited to load files from a list of load paths.

Assuming Venice has been configured with the load paths: [ "/Users/foo/resources" ]

When passing relative paths to these two vulnerable functions everything is fine: (load-resource "test.png") => loads the file "/Users/foo/resources/test.png" (load-resource "../resources-alt/test.png") => rejected, outside the load path

When passing absolute paths to these two vulnerable functions Venice may return files outside the configured load paths: (load-resource "/Users/foo/resources/test.png") => loads the file "/Users/foo/resources/test.png" (load-resource "/Users/foo/resources-alt/test.png") => loads the file "/Users/foo/resources-alt/test.png" !!! The latter call suffers from the Partial Path Traversal vulnerability.

This issue’s scope is limited to absolute paths whose name prefix matches a load path. E.g. for a load-path "/Users/foo/resources", the actor can cause loading a resource also from "/Users/foo/resources-alt", but not from "/Users/foo/images".

Versions of Venice before and including v1.10.16 are affected by this issue.

Patches

Upgrade to Venice >= 1.10.17, if you are on a version < 1.10.17

Workarounds

If you cannot upgrade the library, you can control the functions that can be used in Venice with a sandbox. If it is appropriate, the functions load-file and load-resource can be blacklisted in the sandbox.

References

For more information

If you have any questions or comments about this advisory: * Open an issue in GitHub Venice * Email us at juerg.ch

Credits

I want to publicly recognize the contribution of Jonathan Leitschuh for reporting this issue.

Show details on source website


{
  "affected": [
    {
      "database_specific": {
        "last_known_affected_version_range": "\u003c= 1.10.16"
      },
      "package": {
        "ecosystem": "Maven",
        "name": "com.github.jlangch:venice"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "1.10.17"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2022-36007"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-22"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2022-08-18T19:07:58Z",
    "nvd_published_at": "2022-08-15T11:21:00Z",
    "severity": "MODERATE"
  },
  "details": "### Impact\nA partial path traversal issue exists within the functions `load-file` and `load-resource`. These functions can be limited to load files from a list of load paths.\n\nAssuming Venice has been configured with the load paths: `[ \"/Users/foo/resources\" ]` \n\nWhen passing **relative** paths to these two vulnerable functions everything is fine:\n`(load-resource \"test.png\")`   =\u003e loads the file \"/Users/foo/resources/test.png\"\n`(load-resource \"../resources-alt/test.png\")`   =\u003e rejected, outside the load path\n\nWhen passing **absolute** paths to these two vulnerable functions Venice may return files outside the configured load paths:\n`(load-resource \"/Users/foo/resources/test.png\")`   =\u003e loads the file \"/Users/foo/resources/test.png\"\n`(load-resource \"/Users/foo/resources-alt/test.png\")`   =\u003e loads the file \"/Users/foo/resources-alt/test.png\" !!!\nThe latter call suffers from the _Partial Path Traversal_ vulnerability.\n\nThis issue\u2019s scope is limited to absolute paths whose name prefix matches a load path. E.g. for a load-path `\"/Users/foo/resources\"`, the actor can cause loading a resource also from `\"/Users/foo/resources-alt\"`, but not from `\"/Users/foo/images\"`.\n\nVersions of Venice before and including v1.10.16 are affected by this issue.\n\n### Patches\nUpgrade to Venice \u003e= 1.10.17, if you are on a version \u003c 1.10.17\n\n### Workarounds\nIf you cannot upgrade the library, you can control the functions that can be used in Venice with a sandbox. If it is appropriate, the functions `load-file` and `load-resource` can be blacklisted in the sandbox.\n\n### References\n  * [PR](https://github.com/jlangch/venice/pull/4/commits/c942c73136333bc493050910f171a48e6f575b23)\n \n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [GitHub Venice](https://github.com/jlangch/venice)\n* Email us at [juerg.ch](mailto:juerg.ch@ggaweb.ch)\n\n### Credits\n\nI want to publicly recognize the contribution of [Jonathan Leitschuh](https://github.com/JLLeitschuh) for reporting this issue.",
  "id": "GHSA-4mmh-5vw7-rgvj",
  "modified": "2022-08-18T19:07:58Z",
  "published": "2022-08-18T19:07:58Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/jlangch/venice/security/advisories/GHSA-4mmh-5vw7-rgvj"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2022-36007"
    },
    {
      "type": "WEB",
      "url": "https://github.com/jlangch/venice/commit/215ae91bb964013b0a2d70718a692832d561ae0a"
    },
    {
      "type": "WEB",
      "url": "https://github.com/jlangch/venice/commit/c942c73136333bc493050910f171a48e6f575b23"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/jlangch/venice"
    },
    {
      "type": "WEB",
      "url": "https://github.com/jlangch/venice/releases/tag/v1.10.17"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:N",
      "type": "CVSS_V3"
    }
  ],
  "summary": "Venice vulnerable to Partial Path Traversal issue within the functions `load-file` and `load-resource`"
}


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…