MISP Event Search Discloses Hidden Attribute and Object Data via Missing Sub-Entity Authorization
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 introduces a visibleElementConditions() helper in the Event model that wraps every attribute- and object-level search subquery with the same distribution, sharing-group, and soft-deleted visibility rules enforced by MispAttribute::buildConditions(). New helper methods (visibleAttributeTagSubquery, visibleAttributeTagEventIds, visibleAttributeTagConditions) apply the same checks to tag-based filters. All search code paths in EventsController, Event, MispAttribute, MispObject, and ReportFromEvent now pass the authenticated user into these helpers so that sub-entities hidden from the user no longer influence search results.
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/a01c82ea2 |
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | MISP contains an authorization bypass in its event search and filter functionality. When a user performed searches through events/restSearch (value, value prefix, searchall, type, uuid, attribute tags, object filters), objects/restSearch, or the event index tag, galaxy, and quick filters, the underlying SQL subqueries matched against attributes and objects without enforcing the per-attribute distribution, sharing-group, or soft-deleted visibility rules that apply when fetching individual elements. A user who could view an event (for example, a community-distributed event) could therefore use search to determine whether organisation-only, sharing-group-restricted, or soft-deleted attributes and objects existed within that event. Because the value filter supports prefix matching (LIKE), an attacker could enumerate the full value of a hidden attribute one character at a time. Tags attached exclusively to hidden attributes also leaked through the tag, galaxy, and quick-filter paths on the event index. The vulnerability affects the EventsController quick-filter and index-filter logic, the Event model wildcard/value/uuid/tag filter methods, the MispAttribute tag filter, the MispObject buildFilterConditions and restSearch methods, and the ReportFromEvent object filter. Site administrators and users belonging to the event's own organisation retain full visibility, and sync users continue to match soft-deleted elements as intended. The issue was reported by ENISA. | |
| Title | MISP Event Search Discloses Hidden Attribute and Object Data via Missing Sub-Entity Authorization | |
| First Time appeared |
Misp
Misp misp |
|
| Weaknesses | CWE-200 CWE-862 |
|
| CPEs | cpe:2.3:a:misp:misp:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Misp
Misp misp |
|
| References |
| |
| Metrics |
cvssV4_0
|