Dragonfly Manager makes requests to external endpoints with disabled TLS authentication
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 Manager disables TLS certificate verification in HTTP clients. The clients are not configurable, so users have no way to re-enable the verification. A Manager processes dozens of preheat jobs. An adversary performs a network-level Man-in-the-Middle attack, providing invalid data to the Manager. The Manager preheats with the wrong data, which later causes a denial of service and file integrity problems. This vulnerability is fixed in 2.1.0.
From the CVE record · GitHub_M
Before 2.1.0, Dragonfly Manager HTTP clients disable TLS certificate verification, and users cannot re-enable it. A network-level man-in-the-middle attacker can supply invalid data during preheat jobs, causing later denial of service and file integrity problems. No authentication or user interaction requirements are specified.
Engineers running Dragonfly or using the Go packages github.com/dragonflyoss/dragonfly or d7y.io/dragonfly/v2 before 2.1.0 should check their deployments.