GHSA-8q3c-rjr9-xxrp VictoriaMetrics vmrestore: Path traversal via crafted backup part names escapes restore root

• Go github.com/VictoriaMetrics/VictoriaMetrics: >= 1.137.0, < 1.146.0 → fixed in 1.146.0 • Go github.com/VictoriaMetrics/VictoriaMetrics: >= 1.123.0, < 1.136.12 → fixed in 1.136.12 • Go github.com/VictoriaMetrics/VictoriaMetrics: < 1.122.25 → fixed in 1.122.25

Summary The VictoriaMetrics `vmrestore` utility does not validate backup part path components before writing restored files to the local filesystem. An attacker who can provide or modify a backup source can craft object names containing `..` path components that cause vmrestore to write files outside the intended `-storageDataPath` restore root, subject to the permissions of the `vmrestore` process. Impact An attacker who can supply or modify the backup source -- for example by writing malicious object names to a compromised or misconfigured storage bucket -- can cause arbitrary files to be created or overwritten on the host running `vmrestore`, within the limits of the process's filesystem permissions. Patches Versions 1.146.0, 1.136.12, 1.122.25 Resources • https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.146.0 • https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.136.12 • https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.122.25 Note VictoriaMetrics' security model assumes backup sources are trusted and access-controlled. This vulnerability requires an attacker to have write access to the backup storage (e.g. S3, GCS, or Azure Blob Storage bucket) used as the `-src` for `vmrestore`. Under a correctly secured deployment where backup storage access is properly restricted, unauthorized exploitation of this issue should not be possible. Users are advised to follow the principle of least privilege when granting access to backup storage buckets.