Enisa

#3885من 60,902
77.8إجمالي CVSS
الثغرات · 14
منخفضة
1
متوسطة
13
PT-2026-151609
2026-11-19
3.7
CVE-2026-133190
Misp
Misp
MISP, a threat intelligence sharing platform, contains a vulnerability in its cryptographic key management for protected (PGP-signed) events. Two related defects allow a revoked PGP key to remain effective for signing and validating protected events. First, the validateProtectedEvent() method in the CryptographicKey model iterates over the event's stored cryptographic keys to verify a PGP signature but does not check the revoked flag on each key. A key explicitly marked as revoked is still used to validate signatures, meaning an entity whose key has been revoked can continue to sign protected events and have them accepted by the MISP instance. Second, the captureCryptographicKeyUpdate() method, responsible for synchronizing the key list when a sync user edits a protected event, contained a query bug (find('first') instead of find('all')) that caused only the first stored key to be considered. As a result, revocations of additional keys were never persisted, keys absent from the pushed list were not removed, and entries lacking an explicit fingerprint were mismatched and incorrectly deleted. Additionally, the revocation logic did not enforce the invariant that a revocation, once stored, is never lifted by subsequent pushes. A third minor issue: a signed protected event submitted without any cryptographic keys triggered an unhandled 500 error rather than a proper rejection response. Preconditions: the attacker must be an authenticated sync user with permission to add or edit protected events on the MISP instance. The impact is that revoked keys retain signing authority, key revocations propagated by sync partners are silently dropped, and the integrity of the protected-event trust chain is compromised. In a multi-instance MISP deployment, events signed by revoked keys can propagate to other instances, extending the integrity impact across the sync network.
PT-2026-151492
2026-11-19
6.9
CVE-2026-133175
Misp
Misp
MISP contains an authorization bypass in its server-to-server proposal synchronization mechanism. Two related flaws were identified: 1. The events/pushProposals endpoint located the target event by UUID without enforcing any access-control check. A sync user with perm sync could push shadow-attribute proposals to any event on the local instance, including events with restricted distribution (e.g., distribution level 0, visible only to the owning organisation). The stored proposal also carried the sender-supplied event uuid and event org id rather than the local event's actual identity, corrupting the data model. 2. When accepting an edit proposal (old id != 0), the code resolved the target live attribute by UUID alone (Attribute.uuid = shadow.uuid) without scoping the lookup to the proposal's own event. A malicious sync user could therefore craft a proposal whose uuid matched an attribute in a different event; upon acceptance, the wrong attribute would be modified or deleted. The same unscoped lookup existed in the ShadowAttribute::acceptProposal path. Preconditions: an authenticated user with sync permission (perm sync) on a MISP instance that participates in server-to-server synchronisation. The attacker must know or enumerate the UUID of a target event or attribute. Security impact: unauthorised read access to restricted events, unauthorised insertion of proposals onto events the user cannot see, and unauthorised modification or deletion of attributes belonging to other events. This compromises the confidentiality and integrity of threat-intelligence data across organisational boundaries within a MISP deployment.
PT-2026-151499
2026-11-19
5.3
CVE-2026-133183
Misp
Misp
MISP contains an authorization flaw in the handling of remote pull and feed operations. When a non-internal pull or a feed processes incoming data and encounters an existing sharing group, the application did not verify that the remote server's organization was actually a member of that sharing group before allowing the group's metadata to be updated. The captureRemote mechanism previously stored only a boolean flag indicating whether the link was internal, and the authorization check in captureSGExisting relied solely on that flag. For non-internal pulls and feeds, the check was insufficient: a remote server whose organization was not a member of the target sharing group could still cause the group record to be modified (for example, altering the local flag, the modified timestamp, or other group properties). A feed, which has no associated server organization at all, could likewise trigger an update to an existing sharing group's metadata. The security impact is an integrity violation: an authenticated remote entity with sync or feed privileges can alter sharing group attributes that govern how data is distributed among organizations, potentially changing the local flag or other access-relevant properties of groups it does not belong to. The vulnerability requires an authenticated user with the ability to initiate a pull or feed (a sync user or feed administrator) and a target sharing group that exists on the local instance. No unauthenticated access or user interaction is required.
PT-2026-151608
2026-11-19
6.9
CVE-2026-133188
Misp
Misp
MISP contains a vulnerability in the cryptographic signature verification of protected events. When a MISP instance signs a protected event for synchronization, it strips all whitespace from the JSON body before computing the PGP signature (preg replace("/s+/", "", $data)). The receiving instance performs the same whitespace-stripping before verification. Because the signature covers only the whitespace-free representation, a network relay positioned between two MISP instances can insert whitespace characters into JSON object keys (effectively renaming fields) or into identifier values such as UUIDs, timestamps, and distribution fields without invalidating the signature. The receiving instance accepts the modified event as authentic. The vulnerability affects the protected event synchronization path: event creation (EventsController::add), event editing (EventsController::edit), event viewing (EventsController::view1), and server-to-server pull synchronization (ServerSyncTool, Server model). An attacker with a network position to intercept and modify traffic between MISP instances can alter the semantic content of protected events while the PGP signature still validates, undermining the integrity guarantees that protected events are designed to provide. The fix introduces two complementary mechanisms. First, a post-verification scan rejects any received body that contains whitespace in JSON keys (except under Galaxy cluster 'meta' keys) or in identifier-like values (uuid, id, timestamp, distribution, date). Second, a new exact-byte signature scheme (x-pgp-signature-v2) signs the body as transmitted, without whitespace normalization. MISP 3.0 and later peers exchange this exact-byte signature; older peers retain the legacy whitespace-stripped signature. A signature version field is embedded in protected events so that a 3.0 receiver refuses a body carrying that marker if only the legacy signature is present. Both mechanisms together close the whitespace-injection vector while preserving backward compatibility with pre-3.0 instances.
PT-2026-150933
2026-11-18
5.3
CVE-2026-132636
Misp
Misp
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.
PT-2026-150934
2026-11-18
5.3
CVE-2026-132637
Misp
Misp
يوجد تجاوز للصلاحيات في نقطة النهاية `correlations/eventCorrelations` ومحركات الارتباط الأساسية (Default و OnDemand). لا تتحقق إجراء `CorrelationsController::eventCorrelations` مما إذا كان المستخدم الذي قام بالطلب مسموحًا له بعرض الحدث المحدد بواسطة معلمة `event ID`. يسمح هذا لأي مستخدم مصادق عليه بتزويد معرف حدث ينتمي إلى منظمة أخرى والحصول على نتائج الارتباط الكاملة، بما في ذلك معرفات السمات وقيمها. بالنسبة للأحداث التي يمكن للمستخدم رؤيتها جزئيًا، تقوم محركات الارتباط بتصفية الجانب المستهدف فقط من كل صف ارتباط ولا تدقق في سمات المصدر للحدث المستعلم عنه. نتيجة لذلك، يتم إرجاع الارتباطات المستندة إلى سمات مخفية—مثل السمات الخاصة بالمنظمة أو تلك الموجودة في مجموعات مشاركة مقيدة—مع معرفاتها وقيمها. بالإضافة إلى ذلك، قد تتضمن قائمة الأحداث المرتبطة بمحرك Default المستخدمة في `events/view` أحداثًا مرتبطة فقط من خلال هذه السمات المخفية. يتطلب الاستغلال جلسة مصادقة صالحة ومعرفة أو تعداد لمعرف الحدث المستهدف، مما يؤدي إلى الكشف عن قيم سمات استخبارات التهديدات غير المصرح بها مثل عناوين IP وأسماء النطاقات.
PT-2026-150953
2026-11-18
5.3
CVE-2026-132642
Misp
Misp
MISP contains an access control flaw in its tag management endpoints: events/addTag (single and bulk), events/removeTag, and attributes/removeTag. These endpoints loaded their target event or attribute using an unscoped database query (recursive = -1) that did not apply the calling user's ACL visibility rules. As a result, two distinct security issues existed: (1) Information disclosure: the removeTag endpoint returned different responses depending on whether a given tag was present on a hidden event, allowing an authenticated user to enumerate which tags were applied to events they had no visibility into. (2) Unauthorized modification: users belonging to the host organisation, who are permitted to set local tags on records they can see, could add or remove local tags on events and attributes they could not see, because the canModifyTag ACL check operated on the unscoped object without first verifying the caller's visibility. The fix replaces the unscoped find() calls with ACL-aware fetch methods (fetchSimpleEvent and fetchAttributeSimple) that apply the user's visibility before the object is returned, and adds an explicit empty-object check in removeTag so that a hidden event responds identically to a non-existent one. Affected components include the EventsController (addTag, removeTag), the AttributesController (removeTag), and the ACLComponent (canModifyTag). The vulnerability requires an authenticated user with at least the tagger role (perm tagger) or host-organisation membership.
PT-2026-150955
2026-11-18
6.3
CVE-2026-132644
Misp
Misp
MISP contains an authorization flaw in the GalaxyCluster model's captureCluster() function, which handles the import and synchronization of Galaxy Clusters. Prior to the fix, any authenticated user holding the galaxy editor role could replace an existing locked Galaxy Cluster by supplying its UUID in an import request, regardless of which organization owned the cluster. The function unconditionally called captureOrganisationAndSG() before the save operation, overwriting the cluster's org id and orgc id fields with the importing user's organization, effectively transferring ownership of the cluster to the attacker's organization. Additionally, the save operation was not restricted to a specific set of fields, allowing arbitrary field modification. The vulnerable behavior required the attacker to possess a valid MISP account with the perm galaxy editor role and to know or discover the UUID of a target cluster belonging to another organization. No site-admin or owner-organization privilege was enforced for the update path. The result was that a low-privilege galaxy editor in one organization could modify the content (value, description, distribution, etc.) of clusters owned by other organizations and seize ownership, corrupting the integrity of shared threat-intelligence data across the MISP instance. The vulnerability was reported by ENISA and CERT.pl. The fix introduces an explicit authorization gate that restricts cluster updates to the owner organization, a sync user who can see the cluster via sharing-group rules, or a site administrator, and enforces a field allow-list that excludes org id and orgc id from update writes, preserving original ownership.
PT-2026-150956
2026-11-18
6.3
CVE-2026-132645
Misp
Misp
MISP contains an authorization bypass vulnerability in the Galaxy import/sync functionality (captureGalaxy in app/Model/Galaxy.php). The captureGalaxy() method matched an incoming galaxy payload to an existing galaxy by UUID and unconditionally overwrote the matched record, regardless of whether the importing user belonged to the owning organization or whether the galaxy was a system-provided default galaxy. Any authenticated user holding the perm galaxy editor role could therefore: (1) demote a default galaxy by setting its default flag to false, (2) reassign the galaxy's org id and orgc id to the attacker's organization, effectively taking ownership, and (3) modify other galaxy fields (name, description, distribution, version). Additionally, the role-level permission check (perm site admin or perm galaxy editor) was executed after the captureOrganisationAndSG() call, meaning organization and sharing-group data was already captured before the authorization decision was made. The vulnerability requires an authenticated user with the perm galaxy editor role and the ability to submit a galaxy import payload containing a UUID that matches an existing galaxy. The security impact is loss of data integrity across the MISP instance: default galaxy definitions are corrupted, cross-organization ownership is silently transferred, and the integrity of shared threat-intelligence galaxy metadata is compromised for all users of the instance.