Baja

Cedar: JSON template is in scope missing slot-id validation allows link panic and decision divergence

  • Publicada: 29.10.2026
  • Actualizado: 29.10.2026 18:17

Cedar users must be using all of the following features to be affected by this advisory: JSON format policies, policy templates, and the is in scope condition. This advisory only affects JSON-formatted Cedar policy templates containing is in scope conditions that are malformed according to the Cedar syntax. It does not affect syntactically well-formed policies.

Users of Cedar who author policies in the JSON format were able to write Cedar policies using the is in condition with an incorrect slot identifier in the principal and resource scope constraints (e.g., ?principal in the resource scope constraint) even though this is not allowed when parsing policies from the Cedar policy syntax. Internally, the slot identifiers were silently corrected (e.g. ?resource is placed in the resource scope constraint).

If the policy contains exactly one slot in either the principal or resource position, then any attempt to create a linked policy from the template results in an error: the internal representation of the template does not contain the slot identifier as written in the malformed JSON policy (it has been corrected silently), so attempting to fill that slot is an error. If instead the template is linked using slot identifier expected internally (i.e., not what is written in the JSON template), the linking will initially succeed, but a subsequent invariant violation will cause a panic.

When the template contains slots in both the principal and resource position, then both slots will be present in the internal representation: linking succeeds, but with each slot bound to the value intended for the other (the silent correction). The linked policy is then semantically different from the malformed policy the user intended, and any subsequent authorization decision made against that policy may lead to accesses being unintentionally allowed or denied.

Concretely, consider the following JSON format policy template intended to deny users in a particular project from accessing documents with a particular classification.

{
  "effect": "forbid",
  "principal": {
    "op": "is",
    "entity_type": "User",
    "in": { "slot": "?resource" }
  },
  "action": { "op": "All" },
  "resource": {
    "op": "is",
    "entity_type": "Doc",
    "in": { "slot": "?principal" }
  },
  "conditions": []
}

Linked with ?principal = Classification::"topsecret" and ?resource = Project::"alpha", the author expects to create the policy:

forbid(principal is User in Project::"alpha", action, resource is Doc in Classification::"topsecret");

But because Cedar internally links slots by scope position (not by name), the actual policy evaluated by the engine is:

forbid(principal is User in Classification::"topsecret", action, resource is Doc in Project::"alpha");

If a user is in Project::"alpha" but not Classification::"topsecret", the forbid policy does not apply, and access is unintentionally allowed.

Patches

This advisory is patched in version 4.11.1 and 3.4.3, both available on Crates.io and NPM.

Workarounds

If you cannot update to a patched version, you can determine if you are affected by checking your JSON format policy templates for the following two patterns.

  "principal": {
    "op": "is",
    "entity_type": "User",
    "in": { "slot": "?resource" }
  }

and

  "resource": {
    "op": "is",
    "entity_type": "Doc",
    "in": { "slot": "?principal" }
  }

References

Software afectado

Haz clic en una tecnología para ver todas sus vulnerabilidades.

PlataformaPaqueteVersiones vulnerablesCorregida en
Paquete de npm @cedar-policy/cedar-wasm >= 4.0.1, < 4.11.1, >= 3.2.0, < 3.4.3 4.11.1, 3.4.3

Referencias

Puntuación CVSS -
Vector CVSS
CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:N/VI:N/VA:L/SC:L/SI:L/SA:L
Debilidad (CWE)
CWE-20
Plataforma
npm
Paquete
@cedar-policy/cedar-wasm
Publicada
29.10.2026
Actualizado
29.10.2026 18:17

Fuentes y licencias

OSV / GitHub Advisory Database - GHSA-c33x-vcv4-vg3g - CC BY 4.0

Historial de vulnerabilidades: @cedar-policy/cedar-wasm

Todas las vulnerabilidades publicadas de este paquete (Paquete de npm), de la más reciente a la más antigua. Muestra si es un fallo aislado o un paquete que hay que vigilar.

Esta es la única vulnerabilidad conocida de este paquete.

Identifica las vulnerabilidades de tu aplicación

Con la integración de DockRay y el inventario de software activado, DockRay compara las versiones notificadas de los componentes con las vulnerabilidades conocidas y avisa de las coincidencias confirmadas. La cobertura depende de la tecnología compatible y de los avisos disponibles.

Conectar tu aplicación
Newsletter DockRay

La seguridad de tus aplicaciones en tu correo

Vulnerabilidades importantes, recomendaciones concretas y consejos prácticos para tus aplicaciones. Elige tus tecnologías y sigue lo que importa para tu proyecto.

  • Un resumen diario de nuevas vulnerabilidades, también las críticas.
  • Avisos sobre actualizaciones importantes.
  • Consejos prácticos sobre seguridad y monitorización de aplicaciones.

Déjalo vacío para recibir avisos de todas las tecnologías.

Suscripción gratuita. Date de baja con un clic en cualquier correo.