node-opcua is an OPC UA implementation for TypeScript and Node.js

Why it is Amber

• CVSS 9.1 critical
• Remotely exploitable without logging in
• On your watchlist: node.js

References

• https://github.com/node-opcua/node-opcua/commit/0261e873900800983c622e01120f484dc6063698
• https://github.com/node-opcua/node-opcua/pull/1580
• https://github.com/node-opcua/node-opcua/releases/tag/v2.180.0
• https://github.com/node-opcua/node-opcua/security/advisories/GHSA-xggf-m53x-jc3f

Original description

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.