Microsoft UFO accepts cross-device TASK_END messages by session_id only, allowing peer task-result injection
Microsoft UFO open-source framework for intelligent automation across devices and platforms. In 3.0.1-4-ge2626659, Microsoft UFO's constellation client tracks pending task responses by session_id only and does not verify that a TASK_END message came from the device that originally received the task. When the constellation sends a task to a target device, it records a pending Future under a session key. The pending task record stores the expected device ID, but the completion path ignores that binding. If another authenticated peer device sends a forged TASK_END with the same session_id, the constellation accepts the response and completes the victim device's pending Future with attacker-controlled result data. This is an authenticated cross-device task-result injection issue.
Problem Types
| Type | CWE ID | Description |
|---|
| CWE | CWE-294 | CWE-294: Authentication Bypass by Capture-replay |
| CWE | CWE-345 | CWE-345: Insufficient Verification of Data Authenticity |
Type: CWE
Description: CWE-294: Authentication Bypass by Capture-replay
Type: CWE
Description: CWE-345: Insufficient Verification of Data Authenticity
Metrics
| Version | Base score | Base severity | Vector |
|---|
| 3.1 | 5.9 | MEDIUM | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:L |
Version: 3.1
Base score: 5.9
Base severity: MEDIUM
Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:L