Yeti: Unauthenticated Access to Full Audit Timeline Discloses All Threat Intelligence Data
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| yeti-platform | yeti | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Yeti-platform | Yeti |
|
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.429% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Yeti-platform
Yeti-platform yeti |
|
| Vendors & Products |
Yeti-platform
Yeti-platform yeti |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | Yeti: Unauthenticated Access to Full Audit Timeline Discloses All Threat Intelligence Data | |
| Weaknesses | CWE-306 | |
| References |
| |
| Metrics |
cvssV3_1
|