Homepage

n8n-nodes-base@2.14.0

Base nodes of n8n

  • latest version

    1.121.19

  • first published

    6 years ago

  • latest version published

    9 days ago

  • licenses detected

  • View n8n-nodes-base package health on Snyk  (opens in a new tab)
    • Go back to all versions of this package
    Report a new vulnerability Found a mistake?

    Direct Vulnerabilities

    Known vulnerabilities in the n8n-nodes-base package. This does not include vulnerabilities belonging to this package’s dependencies.

    Fix vulnerabilities automatically

    Snyk's AI Trust Platform automatically finds the best upgrade path and integrates with your development workflows. Secure your code at zero cost.

    Fix for free
    VulnerabilityVulnerable Version
    • M
    LDAP Injection

    n8n-nodes-base is a Base nodes of n8n

    Affected versions of this package are vulnerable to LDAP Injection via the LDAP node's filter escape. An attacker can retrieve unauthorized LDAP records or bypass authentication checks by injecting specially crafted input into LDAP search parameters.

    Note: This is only exploitable if the workflow is configured to pass external user input via expressions into the LDAP node's search parameters.

    How to fix LDAP Injection?

    Upgrade n8n-nodes-base to version 1.121.19, 2.13.1, 2.14.1 or higher.

    <1.121.19>=2.13.0 <2.13.1>=2.14.0 <2.14.1
    • H
    Prototype Pollution

    n8n-nodes-base is a Base nodes of n8n

    Affected versions of this package are vulnerable to Prototype Pollution via the GSuiteAdmin node parameter. An attacker with permissions to create or modify workflows can execute arbitrary code by supplying crafted parameters that pollute Object.prototype during workflow creation or modification.

    How to fix Prototype Pollution?

    Upgrade n8n-nodes-base to version 1.121.19, 2.13.1, 2.14.1 or higher.

    <1.121.19>=2.13.0 <2.13.1>=2.14.0 <2.14.1
    • H
    SQL Injection

    n8n-nodes-base is a Base nodes of n8n

    Affected versions of this package are vulnerable to SQL Injection in the orderByColumn expression of the Data Table Get node. An attacker with permissions to create or modify workflows can execute arbitrary SQL commands by supplying crafted input, potentially leading to unauthorized data access, modification, or deletion.

    Note: This is only exploitable if the Data Table node is enabled.

    How to fix SQL Injection?

    Upgrade n8n-nodes-base to version 1.121.19, 2.13.1, 2.14.1 or higher.

    <1.121.19>=2.13.0 <2.13.1>=2.14.0 <2.14.1
    • H
    Authorization Bypass Through User-Controlled Key

    n8n-nodes-base is a Base nodes of n8n

    Affected versions of this package are vulnerable to Authorization Bypass Through User-Controlled Key via the credential resolution and permission check. An attacker can access and decrypt plaintext secrets belonging to other users by exploiting chained authorization flaws that bypass ownership and project scope checks.

    Note: This is only exploitable if the instance is running the Community Edition and the attacker has the global:member role.

    How to fix Authorization Bypass Through User-Controlled Key?

    Upgrade n8n-nodes-base to version 1.121.19, 2.13.1, 2.14.1 or higher.

    <1.121.19>=2.13.0 <2.13.1>=2.14.0 <2.14.1
    • H
    Command Injection

    n8n-nodes-base is a Base nodes of n8n

    Affected versions of this package are vulnerable to Command Injection via the Execute Command node. An attacker can execute arbitrary commands on the host system by leveraging access to an authenticated user account, potentially leading to data exfiltration, service disruption, or full system compromise.

    Note:

    This is only exploitable if the Execute Command node is enabled and not all user accounts are strictly controlled and trusted.

    This issue does not impact n8n.cloud.

    As per maintainers' memo: "No code changes have been made to alter the behavior of the Execute Command node. The recommended mitigation is to disable the node by default in environments where it is not explicitly required. Future n8n versions may change the default availability of this node."

    ##Workaround

    This vulnerability can be mitigated by disabling the Execute Command node before n8n start using the environment variable: export NODES_EXCLUDE: "[\"n8n-nodes-base.executeCommand\"]".

    How to fix Command Injection?

    There is no fixed version for n8n-nodes-base.

    >=0.1.0
    Go back to all versions of this package