Skip to content

← Public intelligence

Go package

github.com/pydio/cells

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

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

  1. Medium, CVSS 4.3GoPublished

    Go package pydio/cells vulnerable to authorization bypass

    CVE-2023-2978 · GHSA-mv7x-27pc-8c96

    Affected
    • Go github.com/pydio/cells < 4.2.1
    Fixed in
    4.2.1· Vendor fix available
    Issue
    A vulnerability was found in Abstrium Pydio Cells 4.2.0. It has been rated as problematic. Affected by this issue is some unknown functionality of the component Change Subscription Handler. The manipulation leads to authorization bypass. Upgrading to version 4.2.1 is able to address this issue. It is recommended to upgrade the affected component. VDB-230210 is the identifier assigned to this vulnerability.

    Recommended action: Upgrade to 4.2.1 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  2. Medium, CVSS 5.4GoPublished

    go package pydio cells vulnerable to cross-site scripting

    CVE-2023-2981 · GHSA-wmfc-g86p-fjvr

    Affected
    • Go github.com/pydio/cells < 4.2.1
    Fixed in
    4.2.1· Vendor fix available
    Issue
    A vulnerability, which was classified as problematic, has been found in Abstrium Pydio Cells 4.2.0. This issue affects some unknown processing of the component Chat. The manipulation leads to basic cross site scripting. The attack may be initiated remotely. Upgrading to version 4.2.1 is able to address this issue. It is recommended to upgrade the affected component. The identifier VDB-230213 was assigned to this vulnerability.

    Recommended action: Upgrade to 4.2.1 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →