Yeti
Yeti: Unauthenticated Access to Full Audit Timeline Discloses All Threat Intelligence Data
Yeti bridges the gap between CTI and DFIR practitioners by providing a Forensics Intelligence platform and pipeline. Prior to 2.5.1, YETI registers the audit router without Depends(auth.get_current_active_user), and core/web/apiv2/audit.py does not perform a route-level authentication check for /api/v2/audit/timeline/{id}. An unauthenticated network attacker can use an empty, partial, or specific wildcard path to query TimelineLog records containing the actor, target_id, action, and details fields, including analyst usernames, object identifiers and values, and before-and-after object data. This exposes the operational history of threat-intelligence objects while other application routers require authentication. 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.1
Fixed in 2.5.1
Mitigation
Upgrade yeti to 2.5.1 or later.
References
- Vendor advisory github.com/yeti-platform/yeti/security/advisor…
- Patch github.com/yeti-platform/yeti/pull/1276
- Patch github.com/yeti-platform/yeti/commit/692af02ff…
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.