# CVE-2023-32076: in-toto vulnerable to Configuration Read From Local Directory

> Attackers can bypass supply chain integrity checks by placing a malicious .in_totorc file in the working directory to exclude specific files from verification.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 May 2023
- **Updated:** 27 Jan 2025
- **Also known as:** DEBIAN-CVE-2023-32076, GHSA-p86f-xmg6-9q4x, GHSA-wc64-c5rv-32pf, PYSEC-2023-63, UBUNTU-CVE-2023-32076, openSUSE-SU-2026:12182-1

## What is CVE-2023-32076?

CVE-2023-32076 is a medium-severity vulnerability in in-toto, published on 10 May 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-610 (Externally Controlled Reference to a Resource in Another Sphere), CWE-15 (External Control of System or Configuration Setting)

## Which versions are affected by CVE-2023-32076?

3 open source packages ship an affected version, including in-toto. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `in-toto` | PyPI | All versions | 2.0.0 |
| `in-toto` | PyPI | All versions | 2.0.0 |
| `in-toto` | PyPI | All versions | 2.0.0 |
| `in-toto` | openSUSE:Tumbleweed | All versions | 3.1.0-1.1 |

Products: In-Toto Project In-Toto.

## How do I fix CVE-2023-32076?

Upgrade in-toto to 2.0.0 or later.

## Is CVE-2023-32076 being exploited?

There is no known exploitation of CVE-2023-32076 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-32076 and fix it if it is affected.

What it is: CVE-2023-32076 is a medium-severity vulnerability in in-toto, published on 10 May 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-32076 in the wild and no public exploit code.

Affected packages and fixed versions:
- in-toto (PyPI): affected all versions; fixed in 2.0.0
- in-toto (PyPI): affected all versions; fixed in 2.0.0
- in-toto (PyPI): affected all versions; fixed in 2.0.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-32076/ (Markdown: https://insights.sbomify.com/CVE-2023-32076/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-32076
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-32076
- OSV: https://osv.dev/vulnerability/CVE-2023-32076

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-32076/
Summaries are generated and may contain mistakes; the official description above is the record.