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

Medium 5.5 Published Updated

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

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

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, CWE-15

Which versions are affected by CVE-2023-32076?

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

PackageAffectedFixed in
in-toto PyPIAll versions2.0.0
in-toto PyPIAll versions2.0.0
in-toto PyPIAll versions2.0.0
Linux distribution packages (1)
in-toto openSUSE:TumbleweedAll versions3.1.0-1.1

Products include 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.

Sources

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.

Is CVE-2023-32076 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free