You are viewing this page in an unauthorized frame window.
This is a potential security issue, you are being redirected to
https://nvd.nist.gov
An official website of the United States government
Official websites use .gov
A .gov website belongs to an official government organization in the United States.
Secure .gov websites use HTTPS
A lock () or https:// means you've safely connected to the .gov website. Share sensitive information only on official, secure websites.
A vulnerability was identified in the ShadowAttribute proposal creation workflow. The add action accepted user-controlled ShadowAttribute request data without removing the id field before saving the record. Because the underlying framework treats a supplied primary key as an instruction to update an existing record, an authenticated user able to submit shadow attribute proposals could provide the identifier of an existing ShadowAttribute and cause that record to be updated instead of creating a new proposal.
This can result in unauthorized modification of existing shadow attributes, potentially affecting proposals associated with events the user should not be able to alter. Depending on deployment configuration and accessible API responses, the issue may also expose or move proposal data across event contexts.
The vulnerability is caused by trusting a client-supplied primary key during object creation. The fix removes the id field from incoming ShadowAttribute data before processing, ensuring that the endpoint always creates a new proposal rather than updating an existing one. This has been fixed in MISP 2.5.38.
Metrics
NVD enrichment efforts reference publicly available information to associate
vector strings. CVSS information contributed by other sources is also
displayed.
By selecting these links, you will be leaving NIST webspace.
We have provided these links to other web sites because they
may have information that would be of interest to you. No
inferences should be drawn on account of other sites being
referenced, or not, from this page. There may be other web
sites that are more appropriate for your purpose. NIST does
not necessarily endorse the views expressed, or concur with
the facts presented on these sites. Further, NIST does not
endorse any commercial products that may be mentioned on
these sites. Please address comments about this page to [email protected].
Title: MISP, Description: Una vulnerabilidad fue identificada en el flujo de trabajo de creación de propuestas de ShadowAttribute. La acción de añadir aceptaba datos de solicitud de ShadowAttribute controlados por el usuario sin eliminar el campo 'id' antes de guardar el registro. Debido a que el framework subyacente trata una clave primaria proporcionada como una instrucción para actualizar un registro existente, un usuario autenticado capaz de enviar propuestas de atributos sombra podría proporcionar el identificador de un ShadowAttribute existente y hacer que ese registro se actualice en lugar de crear una nueva propuesta.
Esto puede resultar en la modificación no autorizada de atributos sombra existentes, afectando potencialmente propuestas asociadas con eventos que el usuario no debería poder alterar. Dependiendo de la configuración de despliegue y las respuestas de la API accesibles, el problema también puede exponer o mover datos de propuestas entre contextos de eventos.
La vulnerabilidad es causada por confiar en una clave primaria proporcionada por el cliente durante la creación de objetos. La solución elimina el campo 'id' de los datos de ShadowAttribute entrantes antes de procesar, asegurando que el endpoint siempre cree una nueva propuesta en lugar de actualizar una existente. Esto ha sido corregido en MISP 2.5.38.
CPE Deprecation Remap by NIST6/22/2026 3:23:18 PM
Action
Type
Old Value
New Value
Changed
CPE Configuration
OR
*cpe:2.3:a:misp:misp:*:*:*:*:*:*:*:* versions from (including) 2.5.0 from (excluding) 2.5.38
OR
*cpe:2.3:a:misp-project:misp:*:*:*:*:*:*:*:* versions from (including) 2.5.0 from (excluding) 2.5.38
A vulnerability was identified in the ShadowAttribute proposal creation workflow. The add action accepted user-controlled ShadowAttribute request data without removing the id field before saving the record. Because the underlying framework treats a supplied primary key as an instruction to update an existing record, an authenticated user able to submit shadow attribute proposals could provide the identifier of an existing ShadowAttribute and cause that record to be updated instead of creating a new proposal.
This can result in unauthorized modification of existing shadow attributes, potentially affecting proposals associated with events the user should not be able to alter. Depending on deployment configuration and accessible API responses, the issue may also expose or move proposal data across event contexts.
The vulnerability is caused by trusting a client-supplied primary key during object creation. The fix removes the id field from incoming ShadowAttribute data before processing, ensuring that the endpoint always creates a new proposal rather than updating an existing one. This has been fixed in MISP 2.5.38.