Skip to content
Patch Next
Sign inAdd to your agent

← Public intelligence

Go package

github.com/cyphar/filepath-securejoin

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. UnratedGoPublished

    SecureJoin: on windows, paths outside of the rootfs could be inadvertently produced

    GHSA-6xv5-86q9-7xr8

    Affected
    • Go github.com/cyphar/filepath-securejoin < 0.2.4
    Fixed in
    0.2.4· Vendor fix available
    Issue
    Impact For Windows users of github.com/cyphar/filepath-securejoin, until v0.2.4 it was possible for certain rootfs and path combinations (in particular, where a malicious Unix-style /-separated unsafe path was used with a Windows-style rootfs path) to result in generated paths that were outside of the provided rootfs. It is unclear to what extent this has a practical impact on real users, but given the possible severity of the issue we have released an emergency patch release that resolves this issue. Thanks to @pjbgf for discovering, debugging, and fixing this issue (as well as writing some tests for it). Patches c121231e1276e11049547bee5ce68d5a2cfe2d9b is the patch fixing this issue. v0.2.4 contains the fix. Workarounds Users could use filepath.FromSlash() on all unsafe paths before passing them to filepath-securejoin. References See #9.

    Recommended action: Upgrade to 0.2.4 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 →