MISP Object Reference Cross-Event Integrity Violation via UUID Scope Bypass
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| misp | misp | affected |
|
No data.
No data.
No data available yet.
Vendor Solution
The fix adds an event-scope ownership check in ObjectReference::captureReference(). After locating an existing reference by UUID, the code now verifies that the reference's event_id matches the event currently being saved. If the UUID belongs to a different event, the reference is skipped (neither updated nor recreated in the saving event) and a warning-level system log entry is written recording the blocked operation, the target event ID, and the foreign event ID that owns the UUID.
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
No EPSS score available.
Key SSVC decision points have not yet been added.
| Link | Providers |
|---|---|
| https://github.com/MISP/MISP/commit/c9bd0eff5 |
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | MISP contains an authorization and scope flaw in the ObjectReference model's captureReference method. When a user saves an event (via REST API, sync, or feeds), any object reference included in the payload is looked up by its UUID across the entire MISP instance rather than being scoped to the event being saved. An authenticated user with permission to add or edit events can therefore include the UUID of an object reference belonging to a different event—including events in other organizations that the user cannot view—and cause the system to overwrite that foreign reference's relationship_type, comment, deleted flag, and timestamp with attacker-supplied values. The affected reference is neither deleted nor recreated in the attacker's event; its fields are silently rewritten in place. This constitutes a cross-tenant integrity violation: data integrity of object references in events the attacker has no read or write access to is compromised. The vulnerability is reachable through any event save path (REST add/edit, inter-instance sync, feed ingestion) and requires only a valid authenticated session with event modification privileges and knowledge or discovery of a target reference UUID. | |
| Title | MISP Object Reference Cross-Event Integrity Violation via UUID Scope Bypass | |
| First Time appeared |
Misp
Misp misp |
|
| Weaknesses | CWE-639 CWE-640 |
|
| CPEs | cpe:2.3:a:misp:misp:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Misp
Misp misp |
|
| References |
| |
| Metrics |
cvssV4_0
|