Masked namespace vulnerability in Temporal(depthfirst.com)
30 pointsby bmit8 hours ago1 comment
  • haneul6 hours ago
    Even in a product as technically wonderful as Temporal, we can have relatively simple oversights like this that lead to cross tenant leakage.

    If anyone is more familiar with Temporal, is there a way clients could have had internal defense in depth that guards against tenant leakage at the provider (Temporal) level?

    • jiggunjer3 hours ago
      Don't use namespaces. Wire up multi-tenant at the RBAC level. Need stronger isolation? Run another cluster.
    • UltraSane2 hours ago
      Encrypting tenant data with per tenant keys is a good defense against this kind of thing.
    • bdj1086 hours ago
      Things like this are inevitable, especially these days.