More information
#### Details
##### 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.
#### Severity
Moderate
#### References
- [https://github.com/cyphar/filepath-securejoin/security/advisories/GHSA-6xv5-86q9-7xr8](https://togithub.com/cyphar/filepath-securejoin/security/advisories/GHSA-6xv5-86q9-7xr8)
- [https://github.com/cyphar/filepath-securejoin/pull/9](https://togithub.com/cyphar/filepath-securejoin/pull/9)
- [https://github.com/cyphar/filepath-securejoin/commit/c121231e1276e11049547bee5ce68d5a2cfe2d9b](https://togithub.com/cyphar/filepath-securejoin/commit/c121231e1276e11049547bee5ce68d5a2cfe2d9b)
- [https://github.com/cyphar/filepath-securejoin](https://togithub.com/cyphar/filepath-securejoin)
- [https://github.com/cyphar/filepath-securejoin/releases/tag/v0.2.4](https://togithub.com/cyphar/filepath-securejoin/releases/tag/v0.2.4)
This data is provided by [OSV](https://osv.dev/vulnerability/GHSA-6xv5-86q9-7xr8) and the [GitHub Advisory Database](https://togithub.com/github/advisory-database) ([CC-BY 4.0](https://togithub.com/github/advisory-database/blob/main/LICENSE.md)).
Paths outside of the rootfs could be produced on Windows in github.com/cyphar/filepath-securejoin
More information
#### Details
Certain rootfs and path combinations result in generated paths that are outside of the provided rootfs on Windows.
#### Severity
Unknown
#### References
- [https://github.com/cyphar/filepath-securejoin/security/advisories/GHSA-6xv5-86q9-7xr8](https://togithub.com/cyphar/filepath-securejoin/security/advisories/GHSA-6xv5-86q9-7xr8)
- [https://github.com/cyphar/filepath-securejoin/commit/c121231e1276e11049547bee5ce68d5a2cfe2d9b](https://togithub.com/cyphar/filepath-securejoin/commit/c121231e1276e11049547bee5ce68d5a2cfe2d9b)
This data is provided by [OSV](https://osv.dev/vulnerability/GO-2023-2048) and the [Go Vulnerability Database](https://togithub.com/golang/vulndb) ([CC-BY 4.0](https://togithub.com/golang/vulndb#license)).
Release Notes
cyphar/filepath-securejoin (github.com/cyphar/filepath-securejoin)
### [`v0.2.4`](https://togithub.com/cyphar/filepath-securejoin/releases/tag/v0.2.4)
[Compare Source](https://togithub.com/cyphar/filepath-securejoin/compare/v0.2.3...v0.2.4)
This release fixes a potential security issue in filepath-securejoin
when used on Windows (GHSA-6xv5-86q9-7xr8, which could be used to
generate paths outside of the provided rootfs in certain cases), as well
as improving the overall behaviour of filepath-securejoin when dealing
with Windows paths that contain volume names. Thanks to Paulo Gomes for
discovering and fixing these issues.
In addition, we've switched (at long last) to GitHub Actions and have
continuous integration testing on Linux, MacOS, and Windows.
Thanks to the following contributors for making this release possible:
- Aleksa Sarai
- Paulo Gomes
Signed-off-by: Aleksa Sarai
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 has been generated by Mend Renovate. View repository job log here.
This PR contains the following updates:
v0.2.3->v0.2.4SecureJoin: on windows, paths outside of the rootfs could be inadvertently produced
GHSA-6xv5-86q9-7xr8 / GO-2023-2048
More information
#### Details ##### 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. #### Severity Moderate #### References - [https://github.com/cyphar/filepath-securejoin/security/advisories/GHSA-6xv5-86q9-7xr8](https://togithub.com/cyphar/filepath-securejoin/security/advisories/GHSA-6xv5-86q9-7xr8) - [https://github.com/cyphar/filepath-securejoin/pull/9](https://togithub.com/cyphar/filepath-securejoin/pull/9) - [https://github.com/cyphar/filepath-securejoin/commit/c121231e1276e11049547bee5ce68d5a2cfe2d9b](https://togithub.com/cyphar/filepath-securejoin/commit/c121231e1276e11049547bee5ce68d5a2cfe2d9b) - [https://github.com/cyphar/filepath-securejoin](https://togithub.com/cyphar/filepath-securejoin) - [https://github.com/cyphar/filepath-securejoin/releases/tag/v0.2.4](https://togithub.com/cyphar/filepath-securejoin/releases/tag/v0.2.4) This data is provided by [OSV](https://osv.dev/vulnerability/GHSA-6xv5-86q9-7xr8) and the [GitHub Advisory Database](https://togithub.com/github/advisory-database) ([CC-BY 4.0](https://togithub.com/github/advisory-database/blob/main/LICENSE.md)).Paths outside of the rootfs could be produced on Windows in github.com/cyphar/filepath-securejoin
GHSA-6xv5-86q9-7xr8 / GO-2023-2048
More information
#### Details Certain rootfs and path combinations result in generated paths that are outside of the provided rootfs on Windows. #### Severity Unknown #### References - [https://github.com/cyphar/filepath-securejoin/security/advisories/GHSA-6xv5-86q9-7xr8](https://togithub.com/cyphar/filepath-securejoin/security/advisories/GHSA-6xv5-86q9-7xr8) - [https://github.com/cyphar/filepath-securejoin/commit/c121231e1276e11049547bee5ce68d5a2cfe2d9b](https://togithub.com/cyphar/filepath-securejoin/commit/c121231e1276e11049547bee5ce68d5a2cfe2d9b) This data is provided by [OSV](https://osv.dev/vulnerability/GO-2023-2048) and the [Go Vulnerability Database](https://togithub.com/golang/vulndb) ([CC-BY 4.0](https://togithub.com/golang/vulndb#license)).Release Notes
cyphar/filepath-securejoin (github.com/cyphar/filepath-securejoin)
### [`v0.2.4`](https://togithub.com/cyphar/filepath-securejoin/releases/tag/v0.2.4) [Compare Source](https://togithub.com/cyphar/filepath-securejoin/compare/v0.2.3...v0.2.4) This release fixes a potential security issue in filepath-securejoin when used on Windows (GHSA-6xv5-86q9-7xr8, which could be used to generate paths outside of the provided rootfs in certain cases), as well as improving the overall behaviour of filepath-securejoin when dealing with Windows paths that contain volume names. Thanks to Paulo Gomes for discovering and fixing these issues. In addition, we've switched (at long last) to GitHub Actions and have continuous integration testing on Linux, MacOS, and Windows. Thanks to the following contributors for making this release possible: - Aleksa SaraiConfiguration
📅 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.
This PR has been generated by Mend Renovate. View repository job log here.