VictoriaMetrics vmrestore: path traversal via crafted backup part names escapes restore root
VictoriaMetrics
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/VictoriaMetrics/VictoriaMetrics Go |
|
|
VictoriaMetrics
| Product | Affected | Fixed in |
|---|---|---|
| github.com/VictoriaMetrics/VictoriaMetrics Go |
|
|
VictoriaMetrics is a scalable solution for monitoring and managing time series data. Prior to 1.122.25, 1.136.12, and 1.146.0, vmrestore does not validate backup part path components before using lib/backup/actions/restore.go and lib/backup/fslocal/fslocal.go to write restored data below storageDataPath. An attacker who can supply or modify an S3, GCS, Azure Blob Storage, or other backup source can place .. components in object names. When an operator restores that source, the crafted names can create or overwrite files outside the intended restore root within the filesystem permissions of the vmrestore process. This issue is fixed in versions 1.122.25, 1.136.12, and 1.146.0.
From the CVE record · GitHub_M
vmrestore does not validate backup part paths before writing restored data. An attacker who can supply or modify a backup source can use crafted object names to create or overwrite files outside the restore root when an operator restores it, within the vmrestore process's filesystem permissions.
Check deployments using the Go package github.com/VictoriaMetrics/VictoriaMetrics at versions below 1.122.25, from 1.123.0 to before 1.136.12, or from 1.137.0 to before 1.146.0.