Overview
S3Proxy exposes an S3-compatible API in front of other storage. Its filesystem and filesystem-nio2 backends map object keys onto local file paths in the bundled Apache jclouds filesystem provider, and that mapping did not stop traversal sequences.
An authenticated client requests an object key that walks out of the configured storage directory and reads local files from the host. S3Proxy 2.6.0 ships the two jclouds commits that close the hole. No workaround exists short of upgrading.
Affected products
- S3Proxy before 2.6.0 using the filesystem or filesystem-nio2 storage backend
- Apache jclouds filesystem API before 2.7.0
Disclosure timeline
- 02 Feb 2025
- gaul releases S3Proxy 2.6.0 with the fix, on Apache jclouds 2.7.0
- 03 Feb 2025
- GitHub advisory and CVE-2025-24961 published