rattler_cache and py-rattler were vulnerable to package-cache path traversal when handling package metadata from conda channels.
During cache materialization, the ratter_cache code used the package record build string as part of a cache key that was joined into a filesystem path. A malicious or untrusted channel could publish repodata with path separators or traversal components in that field, causing package contents to be written outside the configured package cache directory.
The issue requires use of a malicious or otherwise untrusted conda channel. Curated channels that validate package metadata are not expected to allow malformed build strings of this form.
Users should upgrade to a patched version and avoid untrusted conda channels.
References
rattler_cacheandpy-rattlerwere vulnerable to package-cache path traversal when handling package metadata from conda channels.During cache materialization, the
ratter_cachecode used the package recordbuildstring as part of a cache key that was joined into a filesystem path. A malicious or untrusted channel could publish repodata with path separators or traversal components in that field, causing package contents to be written outside the configured package cache directory.The issue requires use of a malicious or otherwise untrusted conda channel. Curated channels that validate package metadata are not expected to allow malformed build strings of this form.
Users should upgrade to a patched version and avoid untrusted conda channels.
References