pysec-2023-63
Vulnerability from pysec
Published
2023-05-10 18:15
Modified
2023-06-05 01:12
Details

in-toto is a framework to protect supply chain integrity. The in-toto configuration is read from various directories and allows users to configure the behavior of the framework. The files are from directories following the XDG base directory specification. In versions 1.4.0 and prior, among the files read is .in_totorc which is a hidden file in the directory in which in-toto is run. If an attacker controls the inputs to a supply chain step, they can mask their activities by also passing in an .in_totorc file that includes the necessary exclude patterns and settings. RC files are widely used in other systems and security issues have been discovered in their implementations as well. Maintainers found in their conversations with in-toto adopters that in_totorc is not their preferred way to configure in-toto. As none of the options supported in in_totorc is unique, and can be set elsewhere using API parameters or CLI arguments, the maintainers decided to drop support for in_totorc. in-toto's user_settings module has been dropped altogether in commit 3a21d84f40811b7d191fa7bd17265c1f99599afd. Users may also sandbox functionary code as a security measure.

Impacted products
Name purl
in-toto pkg:pypi/in-toto



{
  "affected": [
    {
      "package": {
        "ecosystem": "PyPI",
        "name": "in-toto",
        "purl": "pkg:pypi/in-toto"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "3a21d84f40811b7d191fa7bd17265c1f99599afd"
            }
          ],
          "repo": "https://github.com/in-toto/in-toto",
          "type": "GIT"
        },
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "2.0.0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "0.1.1",
        "0.2.0",
        "0.2.1",
        "0.2.2",
        "0.2.3",
        "0.2.3.dev2",
        "0.2.3.dev3",
        "0.2.3.dev4",
        "0.2.3.dev5",
        "0.2.dev3",
        "0.3.0",
        "0.4.0",
        "0.4.1",
        "0.4.2",
        "0.5.0",
        "1.0.0",
        "1.0.1",
        "1.1.0",
        "1.1.1",
        "1.2.0",
        "1.3.0",
        "1.3.1",
        "1.3.2",
        "1.4.0"
      ]
    }
  ],
  "aliases": [
    "CVE-2023-32076",
    "GHSA-p86f-xmg6-9q4x",
    "GHSA-wc64-c5rv-32pf"
  ],
  "details": "in-toto is a framework to protect supply chain integrity. The in-toto configuration is read from various directories and allows users to configure the behavior of the framework. The files are from directories following the XDG base directory specification. In versions 1.4.0 and prior, among the files read is `.in_totorc` which is a hidden file in the directory in which in-toto is run. If an attacker controls the inputs to a supply chain step, they can mask their activities by also passing in an `.in_totorc` file that includes the necessary exclude patterns and settings. RC files are widely used in other systems and security issues have been discovered in their implementations as well. Maintainers found in their conversations with in-toto adopters that `in_totorc` is not their preferred way to configure in-toto. As none of the options supported in `in_totorc` is unique, and can be set elsewhere using API parameters or CLI arguments, the maintainers decided to drop support for `in_totorc`. in-toto\u0027s `user_settings` module has been dropped altogether in commit 3a21d84f40811b7d191fa7bd17265c1f99599afd. Users may also sandbox functionary code as a security measure.",
  "id": "PYSEC-2023-63",
  "modified": "2023-06-05T01:12:53.259453Z",
  "published": "2023-05-10T18:15:00Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://github.com/in-toto/docs/security/advisories/GHSA-p86f-xmg6-9q4x"
    },
    {
      "type": "ADVISORY",
      "url": "https://github.com/in-toto/in-toto/security/advisories/GHSA-wc64-c5rv-32pf"
    },
    {
      "type": "FIX",
      "url": "https://github.com/in-toto/in-toto/commit/3a21d84f40811b7d191fa7bd17265c1f99599afd"
    },
    {
      "type": "WEB",
      "url": "https://specifications.freedesktop.org/basedir-spec/basedir-spec-latest.html"
    }
  ]
}


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…

Loading…