Yeti
Yeti: Path traversal in DFIQ uuid allows authenticated arbitrary file write during archive export
Yeti bridges the gap between CTI and DFIR practitioners by providing a Forensics Intelligence platform and pipeline. Prior to 2.5.1, core/schemas/dfiq.py accepts an unvalidated uuid from DFIQ YAML through POST /api/v2/dfiq/from_yaml, and core/web/apiv2/dfiq.py later interpolates that stored value into an archive filesystem path in POST /api/v2/dfiq/to_archive. A low-privileged authenticated user can import a DFIQ object whose UUID contains traversal sequences and trigger archive export, causing attacker-controlled content with a .yaml suffix to be written outside the intended temporary archive directory. The impact is limited by paths writable by the YETI service account, and the separate DFIQ archive-import zip-slip candidate is not part of this vulnerability. This issue is fixed in version 2.5.1.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- <= 2.5.0
Mitigation
The record names no fix. Check the vendor advisory below.
References
- Vendor advisory github.com/yeti-platform/yeti/security/advisor…
- Patch github.com/yeti-platform/yeti/pull/1279
- Patch github.com/yeti-platform/yeti/commit/8e36bd000…
1 more
- Release notes github.com/yeti-platform/yeti/releases/tag/2.5…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.