Dragonfly tiny file download uses hard coded HTTP protocol
dragonflyoss dragonfly
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/dragonflyoss/dragonfly Go |
|
|
| d7y.io/dragonfly/v2 Go |
|
|
dragonflyoss dragonfly
| Product | Affected | Fixed in |
|---|---|---|
| github.com/dragonflyoss/dragonfly Go |
|
|
| d7y.io/dragonfly/v2 Go |
|
|
Dragonfly is an open source P2P-based file distribution and image acceleration system. Prior to 2.1.0, the code in the scheduler for downloading a tiny file is hard coded to use the HTTP protocol, rather than HTTPS. This means that an attacker could perform a Man-in-the-Middle attack, changing the network request so that a different piece of data gets downloaded. This vulnerability is fixed in 2.1.0.
From the CVE record · GitHub_M
Before 2.1.0, Dragonfly's scheduler uses HTTP instead of HTTPS when downloading a tiny file. An attacker able to perform a man-in-the-middle attack can change the request so different data is downloaded; authentication and user-interaction requirements are not specified.
Check deployments using Dragonfly or the Go packages github.com/dragonflyoss/dragonfly and d7y.io/dragonfly/v2 before 2.1.0.