Weaviate OSS has path traversal vulnerability via the Shard Movement API
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/weaviate/weaviate Go |
|
|
| Product | Affected | Fixed in |
|---|---|---|
| github.com/weaviate/weaviate Go |
|
|
An issue was discovered in Weaviate OSS before 1.33.4. Due to a lack of validation of the fileName field in the transfer logic, an attacker who can call the GetFile method while a shard is in the "Pause file activity" state and the FileReplicationService is reachable can read arbitrary files accessible to the service process.
From the CVE record · mitre
Weaviate OSS does not validate the fileName field in its transfer logic. An attacker who can call GetFile while a shard is in the "Pause file activity" state and FileReplicationService is reachable can read arbitrary files accessible to the service process. The input does not specify authentication requirements or user interaction.
Operators of github.com/weaviate/weaviate should check versions >=1.30.0 <1.30.20, >=1.31.0-rc.0 <1.31.19, >=1.32.0-rc.0 <1.32.16, and >=1.33.0-rc.0 <1.33.4.