CyberRota Analysis
AI-GeneratedThe vulnerability affects the deepstream server, specifically versions 10.1.0 to 10.1.1, where an oversight in the permission handling allows authenticated users to perform unauthorized modifications to protected records via a PATCH_MULTI operation. This can lead to application state corruption or service disruptions, making it critical for organizations using deepstream to prioritize upgrading to version 10.1.1 to mitigate these risks. Deployments with the default permission type set to none are inherently less affected, as they already permit all operations.
Public Exploit Signal
A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.
Note: these links are listed for security research and verification purposes only.
Original NVD Description
deepstream is a server that allows clients and backend services to sync data, send messages and make rpcs at scale. From 10.1.0 until 10.1.1, src/services/permission/valve/rules-map.ts omits RECORD_ACTION.PATCH_MULTI from RULES_MAP. When an authenticated user sends a PATCH_MULTI record operation while permission.type is config, getRulesForMessage returns a null rule specification and ConfigPermission.canPerformAction treats the missing specification as an unconditional allow instead of applying RULE_TYPES.WRITE. Any authenticated user can therefore modify arbitrary protected records, corrupt application state, or cause service disruption; deployments using the default permission type none already allow all operations and are not additionally affected. This issue is fixed in version 10.1.1.