Node-opcua
node-opcua: Namespace-Level RBAC Fail-Open - Anonymous Write/Call Bypass via Unbound `DefaultRolePermissions
node-opcua is an OPC UA implementation for TypeScript and Node.js. From 2.42.0 until 2.180.0, namespace-level access control configured through setDefaultRolePermissions is not honored by the runtime enforcement path for nodes without explicit per-node RolePermissions. SessionContext.getApplicableRolePermissions reads a missing or null DefaultRolePermissions metadata value instead of the configured namespace field, and the null result is treated permissively. An anonymous network client can consequently write variables with CurrentWrite access or call bound methods when an operator configured a restrictive namespace default and relied on inheritance. Servers with no declared policy, nodes with explicit per-node permissions, and correctly bound programmatic namespace metadata are outside the authorization-bypass case. This issue is fixed in version 2.180.0.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 2.42.0, < 2.180.0
Fixed in 2.180.0
Mitigation
Upgrade node-opcua to 2.180.0 or later.
References
- Vendor advisory github.com/node-opcua/node-opcua/security/advi…
- Patch github.com/node-opcua/node-opcua/pull/1580
- Patch github.com/node-opcua/node-opcua/commit/0261e8…
1 more
- Release notes github.com/node-opcua/node-opcua/releases/tag/…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.