Skip to content

← Public intelligence

npm package

@saltcorn/plugins-loader

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

1 actionable advisory, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. High, CVSS 7.3npmAmendedPublished

    @saltcorn/plugins-loader unsanitized plugin name leads to a remote code execution (RCE) vulnerability when creating plugins using git source

    GHSA-fm76-w8jw-xf8m

    Affected
    • npm @saltcorn/plugins-loader <= 1.0.0-beta.13
    Fixed in
    1.0.0-beta.14· Vendor fix available
    Issue
    When creating a new plugin using the git source, the user-controlled value req.body.name is used to build the plugin directory where the location will be cloned. The API used to execute the git clone command with the user-controlled data is childprocess.execSync. Since the user-controlled data is not validated, a user with admin permission can add escaping characters and execute arbitrary commands, leading to a command injection vulnerability. Details Relevant code from source (req.body) to sink (childprocess.execSync). - file: https://github.com/saltcorn/saltcorn/blob/v1.0.0-beta.13/packages/server/routes/plugins.js#L1400 - file: https://github.com/saltcorn/saltcorn/blob/v1.0.0-beta.13/packages/saltcorn-data/models/plugin.ts#L44 - file: https://github.com/saltcorn/saltcorn/blob/v1.0.0-beta.13/packages/server/loadplugins.js#L64-L65 - file: https://github.com/saltcorn/saltcorn/blob/v1.0.0-beta.13/packages/plugins-loader/plugininstaller.js#L41-L61 - file:…

    Recommended action: Upgrade to 1.0.0-beta.14 (pre-release) or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:osv.dev (1)github.com (2)Source checked Evidence →