NocoBase vulnerabilities

In NocoBase prior to version 2.0.39, the checkSQL() validation function was not applied on the sqlCollection:update endpoint, allowing attackers with collection management permissions to inject arbitrary SQL and exfiltrate data.

The @nocobase/plugin-notification-in-app-message plugin in NocoBase prior to 2.0.61 contains an SQL injection vulnerability via the GET /api/myInAppChannels:list endpoint. The filter[latestMsgReceiveTimestamp][$lt] parameter is directly inserted into a Sequelize.literal() template without sanitization, allowing an authenticated user to execute malicious PostgreSQL queries, potentially including system commands via COPY ... TO PROGRAM.

NocoBase prior to version 2.0.28 contains a vulnerability in the Workflow Script Node that allows an authenticated attacker to escape the Node.js vm sandbox and achieve Remote Code Execution as root via prototype chain traversal using console._stdout and console._stderr.

A vulnerability in NocoBase prior to version 2.1.19 allowed command injection during PostgreSQL backup restoration. An attacker with backup management privileges could inject malicious values into the database.schema field in _metadata.json, which was then interpolated into a shell command executed via child_process.exec().

In NocoBase version 2.0.59 and earlier, the checkSQL() function in the collection-sql plugin fails to block access to PostgreSQL system catalog tables such as pg_shadow, pg_roles, and pg_stat_activity. An admin-role user can read password hashes and database metadata through the SQL Collection feature.

NocoBase up to version 2.1.20 contains a server-side request forgery (SSRF) vulnerability in the serverRequest wrapper. It allows authenticated administrators to issue arbitrary outbound HTTP requests by supplying malicious URLs to workflow request nodes, custom request action buttons, or the AI plugin.

NocoBase prior to version 2.0.30 contains a vulnerability in the plugin-workflow-sql plugin, which substitutes template variables directly into raw SQL strings via getParsedValue() without parameterization or escaping. Any user who triggers a workflow containing a SQL node with template variables from user-controlled data can inject arbitrary SQL.