Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(deps): update dependency flowise to v2 [security] #13

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Aug 3, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
flowise ^1.4.1 -> ^2.0.0 age adoption passing confidence

GitHub Vulnerability Alerts

CVE-2024-31621

An issue in FlowiseAI Inc Flowise prior to v1.8.1 allows a remote attacker to execute arbitrary code via a crafted script to the api/v1 component.

CVE-2024-9148

Flowise < 2.1.1 suffers from a Stored Cross-Site vulnerability due to a lack of input sanitization in Flowise Chat Embed < 2.0.0.

GHSA-5cph-wvm9-45gj

Impact

Flowise allows developers to inject configuration into the Chainflow during execution through the overrideConfig option. This is supported in both the frontend web integration and the backend Prediction API.

This has a range of fundamental issues that are a major security vulnerability.
While this feature is intentional, it should have strong protections added and be disabled by default.

These issues include:

  1. Remote code execution. While inside a sandbox this allows for
  2. Sandbox escape
  3. DoS by crashing the server
  4. SSRF
  5. Prompt Injection, both System and User
  6. Full control over LLM prompts
  7. Server variable and data exfiltration
    And many many more such as altering the flow of a conversation, prompt exfiltration via LLM proxying etc.

These issues are self-targeted and do not persist to other users but do leave the server and business exposed.
All issues are shown with the API but also work with the web embed.

Workarounds

  • overrideConfig should be disabled by default
  • overrideConfig should have an explicit allow list of variables that are allowed to be modified. This way the user opts-in to where modifications can be made.
  • vm2 and any forks of it should be removed as in the authors own words, "fixing the vulnerability seems impossible". The recommended replacement is https://www.npmjs.com/package/isolated-vm

Configuration

📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/npm-flowise-vulnerability branch from f1836c9 to e66be29 Compare August 10, 2024 17:53
@renovate renovate bot force-pushed the renovate/npm-flowise-vulnerability branch from e66be29 to 51a9dd4 Compare August 28, 2024 23:57
@renovate renovate bot changed the title fix(deps): update dependency flowise to v1.8.1 [security] fix(deps): update dependency flowise to v2 [security] Oct 1, 2024
@renovate renovate bot force-pushed the renovate/npm-flowise-vulnerability branch from 51a9dd4 to 118b9b3 Compare October 1, 2024 02:17
@renovate renovate bot force-pushed the renovate/npm-flowise-vulnerability branch from 118b9b3 to dfb3f55 Compare October 27, 2024 13:46
@renovate renovate bot force-pushed the renovate/npm-flowise-vulnerability branch from dfb3f55 to e5ad1d9 Compare October 27, 2024 13:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants